canmove, Confirmed users
1,584
edits
Tree Rules: Difference between revisions
Jump to navigation
Jump to search
Add inbound, aurora, beta, and release. Remove 1.9.0 (firefox3.0) and 1.9.1 (firefox3.5).
m (→mozilla-central - Trunk (Firefox 6): s/Firefox 6/Firefox 10/) |
(Add inbound, aurora, beta, and release. Remove 1.9.0 (firefox3.0) and 1.9.1 (firefox3.5).) |
||
| Line 1: | Line 1: | ||
For comm-central tree rules, [[Tree_Rules/comm-central|see this page]]. | For comm-central tree rules, [[Tree_Rules/comm-central|see this page]]. | ||
== [http:// | == [http://tbpl.mozilla.org/ mozilla-central] - Trunk (Firefox 10) == | ||
'''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. | * '''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree for failures after pushing. | ||
* Please ask in #developers on [[IRC]] if you have questions. | |||
== [https://tbpl.mozilla.org/?tree=Mozilla-Inbound mozilla-inbound] - Inbound == | |||
* '''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules], except you do not need to watch the tree after pushing. | |||
* This tree is merged into mozilla-central approximately daily. | |||
* Please read '''[[Inbound Sheriff Duty]]''' for the commit rules and the list of sheriffs. | |||
* Please ask in #developers on [[IRC]] if you have any questions. | |||
== [https://tbpl.mozilla.org/?tree=Mozilla-Aurora mozilla-aurora] - Aurora (Firefox 9) == | |||
= | '''<font color="orange">APPROVAL REQUIRED</font>''' | ||
* '''All changes''' must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree for failures after pushing. | |||
* have tests, or a strong statement of what can be done in the absence of tests | * 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. | ||
* have landed on | * Patches nominated for beta should: | ||
* have | ** 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 beta. | |||
* Approval requests will be processed by [[Releases/Drivers|release drivers]] in the weekly [[Firefox/Aurora]] meetings. | |||
== [https://tbpl.mozilla.org/?tree=Mozilla-Beta mozilla-beta] - Beta (Firefox 8) == | |||
= | '''<font color="orange">APPROVAL REQUIRED</font>''' | ||
* '''All changes''' must meet the [https://developer.mozilla.org/En/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-beta+''' flag in Bugzilla. To request approval, set the approval-mozilla-beta? flag on the patch you wish to check in. | |||
* Patches nominated for beta should: | |||
** 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 beta. | |||
** not change binary interfaces or otherwise break add-on compatibility. | |||
* Approval requests will be processed by [[Releases/Drivers|release drivers]] in the weekly [[Firefox/Beta]] meetings. | |||
== [https://tbpl.mozilla.org/?tree=Mozilla-Release mozilla-release] - Release (Firefox 7) == | |||
= | '''<font color="orange">APPROVAL REQUIRED</font>''' | ||
Patches | * 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. | ||
* | * 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]]. | ||
== [https://tbpl.mozilla.org/?tree=Firefox3.6 mozilla-1.9.2] - 1.9.2 Branch (Firefox 3.6.x, Gecko 1.9.2.x work) == | |||
= | '''<font color="orange">APPROVAL REQUIRED</font>''' | ||
* patches must have been checked in and "baked" on mozilla-central, | |||
* patches must have '''approval1.9.2.x+''' (for whatever value of x is relevant). | |||
* Set the "status1.9.2" flag to the relevant "fixed .x" value when the patch has been checked into the branch | |||
* patches must have '''approval1.9. | |||
* | |||
Patches nominated for approval1.9.2.x should: | |||
* have tests, or a strong statement of what can be done in the absence of tests | * have tests, or a strong statement of what can be done in the absence of tests | ||
* have landed on trunk and baked for a few days (at least) | * have landed on trunk and baked for a few days (at least) | ||
| Line 62: | Line 60: | ||
* have an assessment of risk | * have an assessment of risk | ||
Please see #developers or today's Sheriff if you have questions. | |||
The branch approval queue is being monitored by [[Releases/Drivers/Branch|branch drivers]], all of whom are usually available on IRC. | The branch approval queue is being monitored by [[Releases/Drivers/Branch|branch drivers]], all of whom are usually available on IRC. | ||