Fix Committed/Fix released

[Robert Collins]

On Fri, 2008-07-18 at 14:23 +1000, Jonathan Lange wrote:
> 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".

Because when I fix something and its not yet merged the correct status
is '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.

Sure. It requires remembering to do that, and pushing the branch to
work. Setting 'Fix Committed' can be done after the fact and doesn't
need the branch to get pushed as a precondition.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080718/fd2b21e1/attachment.pgp