[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Forwarding bugs upstream

On Tue, 2011-01-11 at 18:29 -0700, Drake Wilson wrote:
> Quoth Cyril Brulebois <kibi@debian.org>, on 2011-01-12 01:59:03 +0100:
> > > If a bug is not readily reproducible or isolatable, it may be
> > > necessary to pass it over to an upstream maintainer who will know
> > > what further questions to ask.  But they need to send those
> > > questions to the user, not to the Debian maintainer.  In the kernel
> > > team, we often ask users to report bugs upstream for that reason.
> > 
> > Ditto on the X side. Having a low-power proxy between developers and
> > users is quite a bad idea (induces delays and higher load).
> I tend to think what would be ideal in such cases is for the package
> maintainer to go through the overhead motions of forwarding that
> require a heavy context switch (i.e., setting the ball rolling) and
> then subscribe the user to the relevant bug by email or some other
> similar communication mechanism.
> Which upstream bug trackers, if any, would make the above not work?

Bugzilla requires that each subscribed email address has an account.


Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: