openstack team mailing list archive
Mailing list archive
Re: What each Bug status should mean
On Nov 24, 2010, at 2:51 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx> wrote:
> The first question is what "Fix committed" and "Fix released" should
> mean. There are two possible directions:
> * The developer (or "trunk") view, where "Fix committed" means a branch
> has been proposed with the fix, and "Fix released" means the fix has
> landed in trunk.
> * The user (or "release") view, where "Fix committed" means the fix has
> been committed to trunk and "Fix released" means the fix has been
> released in a given "Openstack release".
> Given the way LP handles "Fix committed" bugs (keep them visible by
> default in bug lists), I tend to prefer the "developer/trunk" view, but
> maybe that is confusing for users (makes it a bit more difficult to find
> already-fixed-in-trunk duplicates when filing a bug against a released
> version ?).
I would pref the user centric view - choices are going to be made about implementations with openstack that are likely to be driven by when a given bug will be resolved in a public release. Having some concrete measure for external people to see which release will resolve it is important.
Likewise, we do lots of work in branches, and as a newcomer to the projet figuring out where a fix has actually landed is a bit tricky - i keep up with trunk, but there is a lot of side work happening, and i dont expect to see the bug resolved as a dedveloper until its in trunk - so i would prefer that interpretation of "fix committed" - that it is committed into trunk.
> The second question revolves around the "Confirmed" and "Triaged"
> states. I would use "Confirmed" when the bug has been acknowledged as a
> real bug and had its "Importance" set. Or should we restrict it to bugs
> that have been strictly reproduced ?
I'm with the others on confirmed means able to reproduce...