Ben Reser <ben@reser.org> writes:
> On Sat, Jan 15, 2005 at 11:16:12PM -0800, Kenneth Porter wrote:
> > They don't track every piece of software they include in the distro, so if
> > a user doesn't let them know that a new version is available, they just
> > don't notice. By plugging it into their tracker, it gets into the queue of
> > things to do.
>
> That still seems really silly IMHO.
It's not uncommon for organizations to use issue trackers to track
tasks... really anything that gets opened, has a life cycle, and
eventually gets resolved can be tracked. I don't think it's silly of
RedHat to use this technique. We do internally at CollabNet all the
time; and the Subversion project has this in its public issue tracker
at times too.
> That's fine. But if they are upstream bugs whoever is the maintainer of
> the package for RedHat should be reporting them to us. Not just letting
> them sit around in their issue tracker.
>
> Ultimately, someone at RedHat who builds the package should have a
> "relationship" with us. As far as I know Joe Orton is responsible for
> the package and he's a committer here. So I'd like to think he does
> that stuff for us.
Yeah. It might or might not be Joe, but I think we can trust that
_someone_ at RedHat will pass native problems upstream.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 19:50:17 2005