launchpad-dev team mailing list archive

[Bjorn Tillenius <bjorn@xxxxxxxxxxxxx>]

Hi Ursula,

could I ask you to write a script that tracks which revisions that have
already been QAed OK? The script would be used in the new merge workflow
that I would propose, but it's something that we could use even for the
next rollout, to see which revision that would be safe to roll out. So
having something ready until then would be great :)

Let me explain how it should work. We need to know which revisions of
devel/db-devel that have been marked as OK in the QA process. But more
importantly, we want to avoid rolling out revisions that haven't been
QAed, so we need to know which consecutive revions thave have been QAed
OK. This is a bit hard to explain, so let me give you an example. Let
say we have the following revisions and their QA statuses:

    r41: OK
    r42: OK
    r43: NEEDS QA
    r44: OK
    r45: NEEDS QA

The script should tell us that r42 should be rolled out. The same is
true if some of the revisions are bad:

    r41: OK
    r42: OK
    r43: BAD
    r44: OK
    r45: NEEDS QA

We will only roll out r44 after r43 has been marked as OK. so if we land
a fix for r43 in r46, we might have something like this:

    r41: OK
    r42: OK
    r43: RCFIXED (r46)
    r44: OK
    r45: NEEDS QA
    r46: OK

In the example above, r42 is still the revision to roll out, since r43
should only be rolled out together with r46, which can't be rolled out
wince r45 hasn't been QA yet.

Do you understand more or less how it should work? We could have a call,
if you need more clarification.

The first step would be to simply tell which revision that is safe to
roll out. The next step is to clearly show which revisions are blocking
other revision from being rolled out. For example, in the last example,
the QA for r45 blocks r43-r46 from being rolled out. A more common
situation will be something like:

    r51: OK
    r52: NEEDS QA
    r53: OK
    r54: OK
    r55: OK
    r56: OK
    r57: OK
    r58: NEEDS QA
    r59: NEEDS QA
    r60: NEEDS QA

In this scenario we need to draw attention to r52 and get it QA as soon
as possible.


-- 
Björn Tillenius | https://launchpad.net/~bjornt