launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxx>]

Perhaps we could apply Lean ideas by taking some data on, each day (or
so), the reason why each unlanded branch is unlanded, choosing one of
these categories:

 * author is not authorized to land it and nobody else has landed it
for them (it looks like there is a 200+ day old branch in this state)
 * tried to land, knocked back because of actual test failures, have
not yet retried
 * tried to land, knocked back because of failures not the fault of this branch
 * wanted to land but couldn't because of testfix mode
 * ...

Or perhaps this would just tell us things we already know by gut feel?

On 24 September 2010 13:53, Maris Fogels <maris.fogels@xxxxxxxxxxxxx> wrote:
> On 09/23/2010 12:19 AM, Martin Pool wrote:
>> I just noticed today there's something like 40 approved ready-to-land
>> reviews on <https://code.edge.launchpad.net/launchpad/+activereviews>,
>> with about 10 over a month old.  It seems like a lot.... Why do you
>> suppose they sit there for so long?
>>
>
> Pure speculation here, but I think that it is partly a side-effect of
> distributed development: you can not easily see where the work is, or where
> undelivered work has built up.  We don't see or count the unmerged branches
> every day (no one person does), and the system, people, and process do not warn
> us when too much undelivered work has built up.

You may be on to something there.   But in fact because of the good
work by the code team, it's actually pretty easy to see how much
outstanding inventory there is in at least one important category:
needs-landing or needs-review branches:

https://code.edge.launchpad.net/launchpad/+activereviews

If that's too big, some things need to get landed; in particular I
would say if it's big because of patches from non-core developers
someone should help them get in.

It may be that this page has become one of those measures that's just
stuck on red (or at least yellow) and people no longer notice?

-- 
Martin