On Sat, Sep 16, 2006 at 08:56:52AM +0200, Christian Perrier wrote: > > AFAIK this bug will be left open until etch is released, then this sarge > > bug will be closed.
> > Steve, Christian do you agree with this, or should we change the > > severity, or close it , or do something else? > Agreed 100%. Even if "sarge" tag is considered obsolete and version > trackig should be used, it is actually convenient to just see that we > should not care about this bug and close it when etch is released, > just the way we closed "woody" bugs when sarge was released. The obsolescence of the suite tags is greatly exaggerated; there is no other method of indicating that a bug's applicability is limited by release, even when it may *not* be limited by version number of the package. > There are a bunch of bugs that are version-tracked as fixed in > "3.0.14whatever' and which should indeed be closed when etch is > released. No, if they're version-tracked as fixed in these versions, they *are* closed and nothing further should be done with them... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
