Formalising the current 'mozilla-central essential pushes only' recommendation

2014-04-07 Thread Ed Morley
(Follow-ups to dev.tree-management please) Hi all :-) The vast majority of mozilla-central landings are now via curated merges from integration/team repositories. This dramatically increases the chance that the tip of mozilla-central is in a known-good state, meaning that: * Integration/pro

Re: Formalising the current 'mozilla-central essential pushes only' recommendation

2014-04-07 Thread Taras Glek
Ed Morley wrote: (Follow-ups to dev.tree-management please) Hi all :-) The vast majority of mozilla-central landings are now via curated merges from integration/team repositories. This dramatically increases the chance that the tip of mozilla-central is in a known-good state, meaning that: *

Re: Formalising the current 'mozilla-central essential pushes only' recommendation

2014-04-07 Thread Randell Jesup
>(Follow-ups to dev.tree-management please) >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 moz

Re: Formalising the current 'mozilla-central essential pushes only' recommendation

2014-06-02 Thread Ed Morley
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: