Tree Rules: Difference between revisions

Jump to navigation Jump to search
1,377 bytes removed ,  9 October 2018
Removed obsolete branches
(updated links to general checkin rules, added ESR 60)
(Removed obsolete branches)
Line 46: Line 46:


Please ask in #developers on [[IRC]] if you have questions.
Please ask in #developers on [[IRC]] if you have questions.
== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora mozilla-aurora] ==
'''<font color="orange">APPROVAL REQUIRED</font>'''
* '''All changes''' must meet the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree for failures after pushing.
* Patches must have the '''approval-mozilla-aurora+''' flag in Bugzilla. To request approval, set the approval-mozilla-aurora? flag on the patch you wish to check in. Exception: If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc).
* Patches nominated for aurora should:
** not change any localizable strings.
** have tests, or a strong statement of what can be done in the absence of tests.
** have landed in mozilla-central to bake on the nightly channel for a few days.
** have a comment in Bugzilla assessing performance impact, risk, and reasons the patch is needed on aurora.
* Approval requests will be processed by the [[Release_Management|release manager]] team.
* Set the appropriate ''status-firefoxN'' flag to "fixed" after landing a fix on the Aurora branch.


== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta mozilla-beta] ==
== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta mozilla-beta] ==
Line 84: Line 70:
* Changes to the release branch are limited to urgent "chemspills" like zero-day security vulnerabilities and other unplanned emergencies.  Any changes to this branch will be directly overseen by the [[Release_Management|release manager]] team.  They are also subject to the same restrictions as [[#mozilla-beta]], including string freeze and UUID freeze.
* Changes to the release branch are limited to urgent "chemspills" like zero-day security vulnerabilities and other unplanned emergencies.  Any changes to this branch will be directly overseen by the [[Release_Management|release manager]] team.  They are also subject to the same restrictions as [[#mozilla-beta]], including string freeze and UUID freeze.


== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-esr52 mozilla-esr52] (Firefox 52.x.y ESR) and [https://treeherder.mozilla.org/#/jobs?repo=mozilla-esr60 mozilla-esr60] (Firefox 60.x.y ESR) ==
== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-esr60 mozilla-esr60] (Firefox 60.x.y ESR) ==


'''<font color="orange">APPROVAL REQUIRED</font>'''
'''<font color="orange">APPROVAL REQUIRED</font>'''


* See [[Release Management/ESR Landing Process]].
* See [[Release Management/ESR Landing Process]].
Confirmed users
38

edits

Navigation menu