[RFC] Bugtracker workflow

[Christian Robottom Reis]

On Sun, Aug 06, 2006 at 08:11:59PM -0500, John Arbash Meinel wrote:
> Having thought about it some more, I think creating a release series
> before each release, so we can earmark what bugs we want to fix before
> it is released would be a good way to work. sabdfl also said that he
> expects something like:
> https://launchpad.net/products/bzr/<series/+bugs
> 
> To be a way to just see the bugs for a particular series (this does not
> work yet).

Note that the URL may not be +bugs to make it clear that this page
doesn't list bugs that are /present/ in that series, but bugs that we
/intend to fix/ in that series. That distinction is important --
targeting a fix to a series is not the same as saying that releases in
that series are affected by that bug.

> So it may be premature, but it would probably be a good way to work with
>  future releases. Though it depends on how well lp ends up working when
> you have 10 release series. Does each series get a box to fill out?
> Which means as the series pile up, the pages get more cluttered?

In the new UI, which is being developed by Brad, you add explicit
targets to series, so there is no risk of unnecessary cluttering. Of
course, if the bug /is/ targeted to be fixed in a number of series, then
yes, you'll have multiple rows in the status table, but that's expected,
given you can control the individual statuses independently.
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125