canmove, Confirmed users
1,126
edits
Tree Rules: Difference between revisions
→mozilla-central (Nightly channel): Update rules for mozilla-central essential pushes only policy change
(Document the standing arrangement with release drivers about a=testonly/a=npotb) |
(→mozilla-central (Nightly channel): Update rules for mozilla-central essential pushes only policy change) |
||
| Line 7: | Line 7: | ||
== [http://tbpl.mozilla.org/ mozilla-central] (Nightly channel) == | == [http://tbpl.mozilla.org/ mozilla-central] (Nightly channel) == | ||
* ''' | * In order to increase the reliability of our primary repository, direct pushes to mozilla-central [https://groups.google.com/d/topic/mozilla.dev.tree-management/V1zZ3JlFpzI/discussion must now] only be for one of the following reasons: | ||
* Set the ''Target Milestone'' field in Bugzilla to the current Nightly version after landing a bug fix on mozilla-central. | ** Merging from an integration/team/project repository (there is no restriction on who may make these merges) [''a=merge'']. | ||
** Automated blocklist / HSTS preload list updates [''a={blocklist-update,hsts-update}'']. | |||
** For the resolution (ie: backout or follow-up fix) of critical regressions (eg: top-crashers or other major functional regression) that will result in a Nightly respin or must make the imminent scheduled Nightly at all costs [''a={backout,topcrasher,respin,...}'']. | |||
** Anything else for which common sense (or asking in #developers) says is an appropriate reason for a direct landing on mozilla-central [''a=something_descriptive'']. | |||
* If your patch is eligible for direct-landing on mozilla-central: | |||
** Use the ''a=reason'' examples given above, to bypass the Mercurial hook used to prevent accidental pushes. Note: That whilst we are using the "a=" syntax (since that's all the hook supports for now), this is unrelated to the "release-driver approval request" process - so please do not request approval from them in Bugzilla. | |||
** Changes must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. | |||
** You must check the tree is green before pushing, notify the sheriffs in #developers and then watch mozilla-central for failures after pushing. | |||
** Set the ''Target Milestone'' field in Bugzilla to the current Nightly version after landing a bug fix on mozilla-central. | |||
* All other changes must instead land via one of the integration branches and will then be merged into mozilla-central once green (these merges occur typically 1-2 times a day on the last complete green push). | |||
* Please ask in #developers on [[IRC]] if you have questions. | * Please ask in #developers on [[IRC]] if you have questions. | ||