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

Re: Closing bugs tagged as $oldstable

Am Montag, den 31.07.2006, 11:19 -0400 schrieb Justin Pryzby:
> On Mon, Jul 31, 2006 at 04:36:24PM +0200, Daniel Leidert wrote:
> > Hello,
> > 
> > Short question, because I wasn't successful to find the answer myself:
> > How are bugs treated, that are tagged as $oldstable (currently woody)?
> Since version tracking is implemented [0], all the "distribution tags"
> mean "this bug should get fixed here (so don't archive the bug)"
> instead of "this bug applies here".

Following the BTS, it reads:

| This bug particularly applies to the woody|potato distribution.

I oversaw, that it was changed for sarge, etch and sid.

> > When these bugs can be closed?
> When $oldstable gets a fixed package, or the maintainer no longer
> intends to persue such a fix.

$oldstable is no longer supported, right? So this means, I could close
those bugs?

> > Or do they have to stay open for all the time?
> I suppose so (*wonders if there will be an $etch+1 tag*).

You mean for the next testing?

> > How do you treat such bugs?
> I'll note that many times these distribution tags may have been set
> before the version tracking was implemented (or before the person
> setting the tag knew how to use it).  So, if there's reason to believe
> this, and reason to believe that the maintainer doesn't actually
> intend to support woody, then the tag could be removed.

... and the bug closed, when it is already solved or not longer
reproducible in >= Sarge?

The reason, why I ask: I have 2 bugs open in a package and both only
apply to Woody, but not to Sarge, Etch or Sid. So I want to know, when
or under which circumstances I can close or "drop" them.

Thanks and regards, Daniel

Reply to: