launchpad-dev team mailing list archive

[Robert Collins <robert.collins@xxxxxxxxxxxxx>]

On Tue, Nov 2, 2010 at 12:19 PM, Maris Fogels
<maris.fogels@xxxxxxxxxxxxx> wrote:
> On 11/01/2010 06:58 PM, Robert Collins wrote:
>> Now that we're doing RFWTAD, I'd like to change our release process.
...
>> To:
>> merge db-devel to devel
>> lock down devel landings (to release-critical)
>> while unqaed: qa
>> choose the rev of devel
>> unlock things
>> @scheduled time: release

> Very nice.  This could make the rollout process much faster and less stressful.
>
> I noticed one point missing from this summary: the use of a full weekend staging
> update to gauge the rollout downtime, and presumably to forecast the clean
> application of all DB patches from the last week.  This update also has the
> unfortunate potential to block all QA for patches landed after Monday.

So, we'd do that friday or so. That is the 'merge db-devel to devel'
step - it will trigger the update.

> I do not see the database update steps mentioned in your summary.  Are they
> something we should think about?  Can we work them into, or out of, a shorter
> release process?

Well the release /itself/ is unaffected by this change, other than the
branch to use (stable rather than production-stable).

-Rob