Fix Committed/Fix released

[Jonathan Lange]

On Fri, Jul 18, 2008 at 9:29 AM, Martin Pool <mbp at canonical.com> wrote:
> On 7/17/08, 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).
>>
>>  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.
>

We would like to provide this feature in Launchpad.

> (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...)

Well... we target bugs and specs to milestones. They then work a
little like a todo list that we update over a release period. We mark
the bugs as fix released after the release, but it's generally not too
cumbersome.

In terms of manual churn, using Fix Committed to mean fix committed
and Fix Released to mean fix released is no worse than your current
process. The difference is just that the churn happens at release time
rather than at pqm-landing time.

jml