Re: [Openstack] What each Bug status should mean

2010-11-24 Thread Joseph Heck
On Nov 24, 2010, at 2:51 AM, Thierry Carrez 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" me

Re: [Openstack] What each Bug status should mean

2010-11-24 Thread Jay Pipes
On Wed, Nov 24, 2010 at 7:46 AM, Soren Hansen wrote: > 2010/11/24 Thierry Carrez : >> 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

Re: [Openstack] What each Bug status should mean

2010-11-24 Thread Eric Day
On Wed, Nov 24, 2010 at 11:51:02AM +0100, Thierry Carrez wrote: > The first question is what "Fix committed" and "Fix released" should > mean. There are two possible directions: I'm good either way, I think both side are valid. > The second question revolves around the "Confirmed" and "Triaged" >

Re: [Openstack] What each Bug status should mean

2010-11-24 Thread Soren Hansen
2010/11/24 Thierry Carrez : > 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

[Openstack] What each Bug status should mean

2010-11-24 Thread Thierry Carrez
Hello everyone, During the weekly IRC meeting yesterday we started a discussion on what meaning we should give to the Launchpad bug statuses for Openstack. It became quickly obvious that there were several worthy options and that the mailing-list was a better forum to discuss this. The first ques