On 18 October 2010 11:23, Julian Edwards <[email protected]> wrote: > On Monday 18 October 2010 00:52:31 Robert Collins wrote: >> What do we need to do as developers? >> - QA as rapidly as possible (and as thoroughly : the outcome of the >> qastaging step is 'ok to deploy'). Use qa-bad and bad-revision=12345 >> tags to mark revisions that must not be deployed. >> - If a revision is bad fixing it is a stop-the-line event : no other >> deployments will happen until its fixed. Use revert liberally - its >> the fastest way to restore to a known good state. > > How do you want these marked if they are qa-bad but we can still roll with > them? i.e. we tried to fix something, didn't get it right, but nothing was > broken more than it was already. >
Also, how does this apply to servers like loganberry? I've got a qa-ok branch for checkwatches that needs to be rolled out thereto; does that need LOSA intervention or will it be auto rolled-out? -- Graham Binns | PGP Key: EC66FA7D http://launchpad.net/~gmb _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
