Hi everyone, I've just revised the DB user section of the DB change policy[1] to require that new users, or access to existing users from new machines, must be set up on production before a branch requiring the change is landed. Previously this was only required at some point before the branch was deployed.
This is similar to our rules around the sequencing of model and DB patches, where we now require prerequisite changes to be entirely deployed before anything dependent can land. Moving these deployment sequence points to pre-landing makes deployments faster, easier and safer. I believe the slight delays brought by the policies to some landings are a good trade-off here. Thanks, William [1] <https://dev.launchpad.net/PolicyAndProcess/DatabaseSchemaChangesProcess#Notes_on_Changing_security.cfg>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
