[RFC] Bugtracker workflow
John Arbash Meinel
john at arbash-meinel.com
Sat Aug 5 17:30:25 BST 2006
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'.
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.
Perhaps working on bzr has made me think too much in a 'history
preservation' mode.
John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060805/8c493904/attachment.pgp
More information about the bazaar
mailing list