Fix Committed/Fix released

[Martin Pool]

On 7/17/08, Robert Collins <robertc at robertcollins.net> wrote:
> On Thu, 2008-07-17 at 11:32 +0100, James Westby wrote:
>
>  > I believe that's how the field is intended to be used, but Bazaar
>  > currently does it the way Daniel described. There was some
>  > discussion at the last sprint about this, and I would favour
>  > switching. One of the things that was standing in the way was
>  > that it would be quite a lot of effort for the release manager
>  > to do this. I volunteered to write a script to automate this, but
>  > I haven't done so, my apologies.
>  >
>  > What else would be stopping us from switching? Would having
>  > that script be enough?
>
>
> 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).
>
>  Running a script would work too I guess.

I think either a script or support in Launchpad would be good.  I
don't think it would be efficient to do all these updates by hand.

(I see the Launchpad developers themselves apparently do this, and
also keep many bugs targetted to particular releases even before they
start working on them, which seems to create a huge amount of manual
churn...)

-- 
Martin <http://launchpad.net/~mbp/>