Re: Freeze Please?
On Sat, Feb 08, 2003 at 04:05:35PM -0500, Michael Stone wrote:
> Third, there's no association in the bts for a package version which
> fixes a bug. Really there should be the possibility of more than one
> version, to address things like stable security uploads, which are on a
> seperate branch from unstable uploads. This is a legacy of our
> development model, which really is "we only work on unstable," in which
> case one should just track the latest unstable.
Just adding version information may not be enough.
It may be that a bug in package X isn't package X's fault, but due
to a bug in another package, eg. libc6.
In which case, keeping track of what versions of X are at fault,
is a bit pointless.
What is perhaps needed here is association between bugs, eg:
bug X causes bug Y.
bug X can't be fixed until after bug Y is fixed.
bug X will be fixed automatically when bug Y and Z are fixed.
(other associations may be possible)
This would mean package X could have a bug report "If I use the -XXX
option I get a segmentation fault", which is marked as being caused by
the bug in libc6 "function X segfaults if passed a parameter ....".
Maximizing the chance a user will see the bug report, regardless of how
they encounter the bug.
Similarly, in the above example, when bug Y is fixed, it could close
both bugs automatically, and you would get to see what versions of libc6
cause the bug in package X.
Of course, this is just agreeing with previous posters in that this
needs to be properly designed in to the BTS.
Brian May <email@example.com>