On Mon, 19 Apr 2010 13:32:24 +1200, Michael Hudson <[email protected]> wrote: > 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.
Great, thanks for the information. Should I file an RT or something so that the LOSAs are aware that this will need to be done? > > * 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. Well, it's not like this is going to be a one-time event. Thanks, James _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
