Changes

Jump to: navigation, search

Tree Rules

1,066 bytes added, 05:05, 7 October 2011
Add inbound, aurora, beta, and release. Remove 1.9.0 (firefox3.0) and 1.9.1 (firefox3.5).
For comm-central tree rules, [[Tree_Rules/comm-central|see this page]].
== [http://teststbpl.themastamozilla.com/tinderboxpushlogorg/ mozilla-central] - Trunk (Firefox 10) ==
* '''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.
Please see #developers or == [httphttps://wwwtbpl.googlemozilla.comorg/calendar/embed?srctree=j6tkvqkuf9elual8l2tbuk2umk%40group.calendar.google.com today's SheriffMozilla-Inbound mozilla-inbound] if you have questions.- Inbound ==
== * '''All changes''' must meet the [httphttps://testsdeveloper.themastamozilla.comorg/tinderboxpushlogEn/?Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules], except you do not need to watch the tree=Firefox3after pushing.6 * This tree is merged into mozilla-1central approximately daily.9* Please read '''[[Inbound Sheriff Duty]]''' for the commit rules and the list of sheriffs.2* Please ask in #developers on [[IRC] - 1.9.2 Branch (Firefox 3.6.x, Gecko 1.9.2] if you have any questions.x work) ==
'''When open== [https: <font color//tbpl.mozilla.org/?tree=Mozilla-Aurora mozilla-aurora] - Aurora (Firefox 9) =="orange">RESTRICTED</font>''' to approved checkins only
'''<font color=== Rules ===* patches must have been checked in and "bakedorange" on mozilla-central,* patches must have >APPROVAL REQUIRED</font>'''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 nominated * '''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 approval1failures after pushing.9* Patches must have the '''approval-mozilla-aurora+''' flag in Bugzilla.2To request approval, set the approval-mozilla-aurora? flag on the patch you wish to check in.x * 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 trunk and baked the nightly channel for a few days (at least).** have an assessment of a comment in Bugzilla assessing performance impact, risk, and reasons the patch is needed on beta.* have an assessment of riskApproval requests will be processed by [[Releases/Drivers|release drivers]] in the weekly [[Firefox/Aurora]] meetings.
Please see #developers or today's Sheriff if you have questions== [https://tbpl.mozilla.org/?tree=Mozilla-Beta mozilla-beta] - Beta (Firefox 8) ==
'''<font color=== Patch Approval & Release Driving ===The branch approval queue is being monitored by [[Releases/Drivers"orange">APPROVAL REQUIRED</Branch|branch drivers]], all of whom are usually available on IRC.font>'''
== * '''All changes''' must meet the [httphttps://testsdeveloper.themastamozilla.comorg/tinderboxpushlogEn/?Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules]. You must check the tree before pushing, and watch the tree=Firefox3for failures after pushing.5 * Patches must have the '''approval-mozilla-1beta+''' flag in Bugzilla.9.1] To request approval, set the approval-mozilla- 1beta? flag on the patch you wish to check in.9* Patches nominated for beta should:** have tests, or a strong statement of what can be done in the absence of tests.1 Branch (Firefox 3** have landed in mozilla-central to bake on the nightly channel for a few days.5.x** have a comment in Bugzilla assessing performance impact, risk, Gecko 1and reasons the patch is needed on beta.9** not change binary interfaces or otherwise break add-on compatibility.1* Approval requests will be processed by [[Releases/Drivers|release drivers]] in the weekly [[Firefox/Beta]] meetings.x work) ==
'''When open== [https: <font color//tbpl.mozilla.org/?tree=Mozilla-Release mozilla-release] - Release (Firefox 7) =="orange">RESTRICTED</font>''' to approved checkins only
'''<font color=== Rules ===* patches must have been checked in and "bakedorange" on mozilla-central,* patches must have >APPROVAL REQUIRED</font>'''approval1.9.1.x+''' (for whatever value of x is relevant).* Set the "status1.9.1" flag to the relevant "fixed .x" value when the patch has been checked into the branch
* Patches nominated for approval1must have the '''approval-mozilla-release+''' flag in Bugzilla.9.1To request approval, set the approval-mozilla-release? flag on the patch you wish to check in.x should:* have testsIn the normal development process, or a strong statement of what can be done in the absence of testsno changes will land on mozilla-release except [[RapidRelease/Calendar|regular merges from mozilla-beta]] every six weeks.* have landed on trunk Changes to the release branch are limited to urgent "chemspills" like zero-day security vulnerabilities and baked for a few days (at least)* have an assessment of performance impact* have an assessment of riskother unplanned emergencies. Any changes to this branch will be directly overseen by [[Releases/Drivers|release drivers]].
Please see #developers or today's Sheriff if you have questions== [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=== Patch Approval & Release Driving ===The branch approval queue is being monitored by [[Releases/Drivers"orange">APPROVAL REQUIRED</Branch|branch drivers]], all of whom are usually available on IRC.font>'''
== [http://tinderbox.mozilla.org/Firefox3.0/ Firefox3.0] - Branch (Firefox 3.0.x only) == '''When open: <font color=* patches must have been checked in and "orangebaked">RESTRICTED</font> to branchon mozilla-approved checkins only''' === Rules ===central,* patches must have '''approval1.9.02.x+''' (for whatever version value of x we are currently approving), or not affect the Firefox build (tests, [[NPOTB]] changesis relevant).* add Set the fixed1"status1.9.02" flag to the relevant "fixed .x keyword to " value when the bug when it patch has been checked into the branch Patches nominated for approval-1.9.0.x should:
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 landed on trunk and baked for a few days (at least)
* have an assessment of risk
'''This tree is not sheriff'd.''' Please be sure to monitor for any bustage see #developers or performance regressions on the tree and take the appropriate back out actionstoday's Sheriff if you have questions.
=== Patch Approval & Release Driving ===
The branch approval queue is being monitored by [[Releases/Drivers/Branch|branch drivers]], all of whom are usually available on IRC.
Canmove, confirm
1,584
edits

Navigation menu