>(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 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.
This is why all my hgrc files have no default push target; all have things like: inbound = ssh://hg.mozilla.org/integration/mozilla-inbound/ or beta = ssh://hg.mozilla.org/releases/mozilla-beta/ or m-c = ssh://hg.mozilla.org/mozilla-central/ such that if I forget what directory I'm working with I can't push to the wrong repo. Of course, the default when people clone isn't set that way. requiring CENTRAL or whatever would have the effect of blocking everyone's accidental pushes. I usually land on central for 3 things: want a fix to get into the next nightly and I'm unsure or expect no more merges; inbound has been closed for ages; or it's uplift weekend - even landing Saturday has no guarantee to being in the merge (though *almost* always it is). I sleep better knowing I don't have to worry about when the merge will be done, if it will be done (and I always hang out and star). But I understand the contrary opinion to that last case. And once in a blue moon I'll land a m-c update after an uncorrect uplift (uplift of patch but not the backout) or other fubar. -- Randell Jesup, Mozilla Corp remove "news" for personal email _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
