Hi, We found out today that with the recent changes to the DB deployment process, it wasn't clear what was the situation with landing release-critical changes when devel is in RC-mode.
I've discussed this with Robert and clarified https://dev.launchpad.net/PolicyAndProcess/Downtime In a nutshell, the rules of thumb to apply is: Does landing this change will save us from handling an incident during or shortly after the deployment? In the affirmative, land it without second doubt. (Use release-critical=<you>). For all other cases, it doesn't need a release-critical. Exceptionally, the TA, Product Strategist or I could approve such a branch. But in reality, we don't really want them. With the new process, most of the things can go live using the nodowntime deployment. Let me know if this needs further clarifications. -- Francis J. Lacoste francis.laco...@canonical.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
