[RFC] Bugtracker workflow

[Wouter van Heyst]

On Sat, Aug 05, 2006 at 11:30:25AM -0500, John Arbash Meinel wrote:
> This is just something I've been thinking about. It may not be something
> that we can get Launchpad to support (easily).
> 
> But it seems to me, that bugs should be marked as existing in certain
> releases, and then fixed/closed in others.
> Right now we use the bug tracker as pretty much just a 'the current
> state of bugs'. We have no real way to say, 'This was a known issue in
> bzr-0.8.2, but we fixed it in 0.9'.

The Debian bts has recently grown support for this, see 'found' in
    http://www.debian.org/Bugs/server-control 

For Debian it is rather important, with a huge amount of packages in
several distributions at the same time, the most recent version is not
the only one that matters.

> It could just be that this is the standard way bug trackers work. They
> only keep track of the *current* bug state, not really the state over time.
> 
> Anyway, it seems like we could do something like this with 'Release
> Series' instead of using one series and a bunch of milestones.
> But that could be too much overhead. And also probably leaves it looking
> like we have open bugs, when really we are fixing them in newer releases.

It could be that
https://launchpad.net/products/malone/+spec/series-and-distrorelease-mgmt
supports this, but I can't reach the wiki. If not, your suggestion is
worthy of its own spec imho.

> Perhaps working on bzr has made me think too much in a 'history
> preservation' mode.

*g*

Wouter van Heyst