On 07/04/2014 10:37, Ed Morley wrote:
Non-critical mozilla-central landings are already discouraged and as such are rare. However, the sheriffs [2] would like to formalise this, by adjusting the mozilla-central tree rules [3] to state that direct pushes must be for one of the following reasons:
With the absence of any major objections to proceeding with this, I've updated the tree rules to reflect these changes:
https://wiki.mozilla.org/Tree_Rules#mozilla-central_.28Nightly_channel.29 On 07/04/2014 10:37, Ed Morley wrote:
A proportion of the current mozilla-central non-critical commits are made by people inadvertently pushing to the wrong repository. To prevent these, once the tree rules are adjusted on the wiki the sheriffs envisage the next step will be switching mozilla-central to a non-open tree state (name TBD) using the existing tree closure hook. Backouts, merges & automated bot updates will not need any additional annotation - others will simply use a (yet to be chosen) commit message string to signify awareness & adherence to the new tree policy.
For the short term we'll take advantage of the existing "approval required" tree hook to remind people about the change, until such a point as we have a new named state for it. The wiki changes above describe what to put in the commit message when self-approving (eg a={merge,chemspill,respin,...}).
NB: For the avoidance of doubt, this is similar to the way the "approval required" hook was used for the PGO issues last year - and is not related to the release driver "approval request" workflow in any way.
Cheers, Ed _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
