Tree Rules: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 5: Line 5:
'''When open: <font color="#F88017">RESTRICTED</font>'''. Checkins must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules] and must also meet one of the following criteria:
'''When open: <font color="#F88017">RESTRICTED</font>'''. Checkins must meet the [https://developer.mozilla.org/En/Developer_Guide/Committing_Rules_and_Responsibilities general checkin rules] and must also meet one of the following criteria:


* Patches for bugs that are marked [http://bit.ly/b7freeze blocking2.0:beta7+ or blocking-fennec:2.0b1+]
* Patches for bugs that are marked [http://bit.ly/b7freeze blocking2.0:beta7+ or blocking-fennec:2.0b1+] or any branch blocker that needs to land on trunk first
* Patches that only change test code
* Patches that only change test code
* Patches that are not part of the default build
* Patches that are not part of the default build

Revision as of 14:10, 28 September 2010

For comm-central tree rules, see this page.

mozilla-central - Trunk (Firefox 4.0, Gecko 2.0 work)

When open: RESTRICTED. Checkins must meet the general checkin rules and must also meet one of the following criteria:

  • Patches for bugs that are marked blocking2.0:beta7+ or blocking-fennec:2.0b1+ or any branch blocker that needs to land on trunk first
  • Patches that only change test code
  • Patches that are not part of the default build
  • Bustage fixes
  • Backouts


Please see #developers or today's Sheriff if you have questions.

mozilla-1.9.2 - 1.9.2 Branch (Firefox 3.6.x, Gecko 1.9.2.x work)

When open: RESTRICTED to approved checkins only

Rules

  • 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 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 performance impact
  • have an assessment of risk

Please see #developers or today's Sheriff if you have questions.

Patch Approval & Release Driving

The branch approval queue is being monitored by branch drivers, all of whom are usually available on IRC.

mozilla-1.9.1 - 1.9.1 Branch (Firefox 3.5.x, Gecko 1.9.1.x work)

When open: RESTRICTED to approved checkins only

Rules

  • patches must have been checked in and "baked" on mozilla-central,
  • patches must have 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 approval1.9.1.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 performance impact
  • have an assessment of risk

Please see #developers or today's Sheriff if you have questions.

Patch Approval & Release Driving

The branch approval queue is being monitored by branch drivers, all of whom are usually available on IRC.

Firefox3.0 - Branch (Firefox 3.0.x only)

When open: RESTRICTED to branch-approved checkins only

Rules

  • patches must have approval1.9.0.x+ (for whatever version of x we are currently approving), or not affect the Firefox build (tests, NPOTB changes)
  • add the fixed1.9.0.x keyword to the bug when it has been checked into the branch

Patches nominated for approval-1.9.0.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 performance impact
  • have an assessment of risk

This tree is not sheriff'd. Please be sure to monitor for any bustage or performance regressions on the tree and take the appropriate back out actions.

Patch Approval & Release Driving

The branch approval queue is being monitored by branch drivers, all of whom are usually available on IRC.