Fix Committed/Fix released

[Jonathan Lange]

On Thu, Jul 17, 2008 at 8:41 PM, Robert Collins
<robertc at robertcollins.net> wrote:
> So, at the moment its very low key for developers to manage this status.
> We spend more time per capita in the bug database than users; I think we
> should continue to keep the overhead low. As such, as long as I don't
> have to fight things to keep the metadata up to date I don't care how we
> manage it (e.g. 'fix available' on a branch takes what - 4 round trips?
> Thats about 2 minutes from Sydney vs 1 round trip to expand the drop
> down and set to fix committed today).
>

Setting "fix released" takes the same time as "fix committed"—I'm not
sure why you mention "fix available".

For what it's worth, you can set 'fix available' on a bug with zero
roundtrips to the webapp: just do 'bzr ci --fixes lp:12345' on a
branch that is hosted on or mirrored to Launchpad.

jml