On Mon, May 30, 2005 at 10:21:45AM -0700, Russ Allbery wrote: > Roger Leigh <[EMAIL PROTECTED]> writes:
> > That's still requiring /manual intervention/, and lying about the true > > state of the bug to the BTS. Ideally the BTS should understand that the > > bug was closed by a particular version of the package (the one which had > > Closes: in it), and the bug is still present in earlier versions > > (perhaps it should also have the ability to record the version the bug > > appeared in as well). The BTS should be able to know that a bug is > > closed in testing automatically, rather than me sending messages to > > [EMAIL PROTECTED]; I must have sent at least 30 the past week alone. > Another somewhat related matter that's bothered me for a while is that > right now the Debian bug tracking system is not particularly useful for > users of the stable version. The BTS is not likely to have much sign of > most of their bugs, the maintainers have to carry around stable-tagged > bugs (that then may show up as RC bugs in various summary reports) in > order to document stable issues that are already fixed in unstable or > testing, and the whole situation seems a bit confusing to what we would > anticipate is the "average" Debian user (someone who uses stable). > I'm not sure what the best fix is. Obviously, most bugs can't be fixed > for stable -- even a lot of RC bugs are questionable to fix for stable > once it's actually released. It would still be nice to give the user the > known information about a bug they're running into, including any > workarounds that had been found. That would be the BTS version tracking support, which is slated to be deployed immediately post-sarge. -- Steve Langasek postmodern programmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
