On Mon, Mar 03, 2008 at 01:55:29PM -0800, Don Armstrong wrote: > On Mon, 03 Mar 2008, Colin Watson wrote: > > On Mon, Mar 03, 2008 at 10:01:00PM +0100, Steinar H. Gunderson wrote: > > > On Mon, Mar 03, 2008 at 08:57:25PM +0000, Colin Watson wrote: > > > > Blink. Is that a typo? notfixed should be, if anything, the opposite of > > > > -done. If what you say is the case then I think we (or indeed probably > > > > I) buggered up the semantics rather badly. > > > I guess what he was trying to say, was that a versioned close + notfixed > > > is > > > the same as an unversioned close. (notfixed removes the version, but does > > > not > > > change the status of the bug.) > > Ah. For the record I am inclined to think that is at best unintuitive > > and probably a bug. > We need a command that does what notfixed does.
Well, ultimately, the problem's that "done" doesn't really mean all that
much anymore -- we've got:
real bugs that applied in version between X and Y
real bugs that applied in versions >= X
real bugs that can't be associated with a version because they
apply to pseudopackages, or to packages not in the archive
things that should never have been reported as bugs
We could introduce a pseudoversion for pseudopackages, eg make it the day
in UTC formatted as YYYY.MM.DD -- then we can require a Version to always
be present, and deal with things as:
filed/closed bug against a real package, versions should be
as expected
filed against a pseudopackage -- version should be the date the
bug first appeared
closed bug against a pseudopackage -- version should be the date
the bug was fixed
version of a pseudopackage in stable/testing/unstable == today's
date; pseudochangelog for pseudopackages that gives it a daily
history
closing a bug that should never have existed: just mark it
notfound in any version and not fixed in any version (or mark
it fixedin every version that it's foundin)
The done field could then either be dropped entirely, or left as a comment
that's only displayed for bugs that're determined to be resolved purely
by looking at versions.
For a version-free view (ie without dist=unstable, etc), you might be
able to determine open/resolved based on based on whether max(found-in)
> max(fixed-in). You'd need to have something, to avoid relying on the
done field.
Cheers,
aj
signature.asc
Description: Digital signature
