launchpad-dev team mailing list archive

[Michael Hudson <michael.hudson@xxxxxxxxxxxxx>]

On 17/04/10 02:01, James Westby wrote:
> Hi,
>
> Last release Michael helped us with the critical task of branching
> Ubuntu on its release.
>
> We will be able to make use of much of that work again this time, but I
> want to make sure we are ready for it.
>
>    * Does the script that was used last time need to be updated for
>      anything? (Where is it?)

It's in the launchpad tree, scripts/branch-distro.py

>    * What needs to happen for us to do this? Do we need to reserve some
>      LOSA time, or at least make them aware we are going to do this?

It's on https://wiki.ubuntu.com/NewReleaseCycleProcess, but only as:

# Notify James Westby/Jonathan Lange to initialize the branches for the 
new series.

We'll need to run:

./scripts/branch-distro.py -v ubuntu lucid maverick

And at the end of the run we need to run something like:

update branch set next_mirror_time = CURRENT_TIMESTAMP AT TIME ZONE 
'UTC' where id in (select branch from seriessourcepackagebranch where 
distroseries in (select distroseries.id from distroseries, distribution 
where distroseries.name in ('lucid', 'maverick') and distribution.name = 
'ubuntu'))

to trigger the puller to run.  Last time this clogged up the branch 
puller queue for several hours, so maybe we should run something like:

update branch set next_mirror_time = CURRENT_TIMESTAMP AT TIME ZONE 
'UTC' where id in (select branch from seriessourcepackagebranch where 
distroseries in (select distroseries.id from distroseries, distribution 
where distroseries.name in ('lucid', 'maverick') and distribution.name = 
'ubuntu' limit 500))

every so often until it doesn't update any rows, or something that 
spreads next_mirror_time for these branches evenly over the next 10 hours.

>    * Anything I have forgotten?

The timing hasn't really worked out, but I'm working on removing the 
hosted/mirrored split for Launchpad branches, so next time the script 
will be simpler and faster, as well as not needing to do the 
next_mirror_time frobbing.

Cheers,
mwh