This will give us a way to land potentially disruptive changes (e.g., upgrading puppet) without affecting production systems. It will be a bit more annoying in that we'll need to merge changes back and forth to the moco repository, but that shouldn't be so bad if we don't require review for merges *to* relabs, but do require review for merges *from*, and try to limit the number of "fix a typo" commits to the relabs repo. (this sprang from the canary discussion in email - this would be a layer *before* the canary layer for changes that might disrupt production even in the canary stage).
OK, this is now running from http://hg.mozilla.org/build/relabs-puppet/graph
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.