Tree Rules: Difference between revisions

Jump to navigation Jump to search
19 bytes removed ,  18 March 2015
m
more link fixes for relman stuff
m (→‎mozilla-aurora: fixed link!)
m (more link fixes for relman stuff)
Line 58: Line 58:
** have landed in mozilla-central to bake on the nightly channel for a few days.
** 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 beta.
** have a comment in Bugzilla assessing performance impact, risk, and reasons the patch is needed on beta.
* Approval requests will be processed by [[Releases/Drivers|release drivers]] in the weekly [[Firefox/Channels]] meetings.
* Approval requests will be processed by by the [[Release_Management|release manager]] team.
* Set the appropriate ''status-firefoxN'' flag to "fixed" after landing a fix on the Beta branch.  
* Set the appropriate ''status-firefoxN'' flag to "fixed" after landing a fix on the Beta branch.  


Line 67: Line 67:
* Patches must have the '''approval-mozilla-release+''' flag in Bugzilla. To request approval, set the approval-mozilla-release? 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 must have the '''approval-mozilla-release+''' flag in Bugzilla. To request approval, set the approval-mozilla-release? 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).
* In the normal development process, no changes will land on mozilla-release except [[RapidRelease/Calendar|regular merges from mozilla-beta]] every six weeks.
* In the normal development process, no changes will land on mozilla-release except [[RapidRelease/Calendar|regular merges from mozilla-beta]] every six weeks.
* 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 [[Releases/Drivers|release drivers]].  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-b2g34_v2_1 mozilla-b2g34_v2_1] (and other B2G branches) ==
== [https://treeherder.mozilla.org/#/jobs?repo=mozilla-b2g34_v2_1 mozilla-b2g34_v2_1] (and other B2G branches) ==
Confirmed users
2,816

edits

Navigation menu