An interesting read when discussing what to do about our bugs...

[Ralf Corsepius]

On Wed, 2008-01-23 at 16:06 -0500, Alan Cox wrote:
> On Wed, Jan 23, 2008 at 02:20:01PM -0600, Jon Ciesla wrote:
> > >> specific breakage to be proactive and tap into the upstream resource
> > >> when I can't confirm the problem.
> > >
> > > There is a huge difference between engaging the user and helping them
> > > to contact upstream, or getting upstream in contact with the user,
> > > basically facilitating that wonderful communication, and saying "Shut
> > > up, that's upstream, go away" and closing the bug.
Unfortunately, the latter also happens.

> > Very true, it MUST be a collaborative exercise.
> 
> I try to leave the RH bug open and even if I report it being an upstream
> problem then update it now and again with the status of things. That way
> people at least know something is happening and when it will be worth trying
> an update
Fully agreed, that's the only viable and reasonable approach.

Ralf