== Problem == We are very close to our 3.1.10 rollout and we do not have our lp_db buildbot instance to check db-devel before merging it into db-stable, so the last automatic merge into db-stable was on 2009-10-29 and included stable r9806. '''No longer necessary - we now have a functioning buildbot for db-lp''' We are scheduled to release in just over 24hrs, which means that we are scheduled to close devel in a little over an hour (at 0900 UTC). We are therefore dependent on tested db-devel reaching db-stable and being updated on staging for QA. == Proposal == We can continue submitting to db-devel via pqm, but need to manually run ec2 test for db-devel revisions and manually merge db-devel -> db-stable. Unfortunately we cannot run the ec2 test with the normal launchpad-slave-db-devel-* ami used by lp_db, but mwhudson says: "the launchpad-ec2test100 ami was built by the code in ec2 test itself so you can see what's there (much more so than we can for the buildbot images fwiw)". Also, because we have not had any updates to db-stable since 8620, we will probably need to update staging with db-stable as we go so that QA can be done. == db-devel test Log == == db-devel -> stable merge log == * db-devel r8630 sent off at 20091103 0805UTC by noodles (./utilities/ec2 test --headless -b launchpad=db-devel)<
> [[http://pastebin.ubuntu.com/308393/|Successful]] == Staging update of stable ==