Tree Rules: Difference between revisions

Revision as of 10:24, 2 May 2012

For comm-central tree rules, see this page.

Not sure which Firefox version is on which branch today? See RapidRelease/Calendar.

APPROVAL REQUIRED because of bug 750661.
- If your patch touches only files that are not part of the Windows libxul build then you have automatic approval to land. In your commit message, use a=mac-only, a=android-only, a=js-only, a=chrome-only, a=npotb etc.
- If in doubt, please ask in #developers first!
All changes must meet the general checkin rules. You must check the tree before pushing, and watch the tree for failures after pushing.
Set the Target Milestone field in Bugzilla to the current Nightly version after landing a bug fix on mozilla-central.
Please ask in #developers on IRC if you have questions.

All changes must meet the 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 Tree Rules/Inbound for commit procedures and the list of sheriffs.
Ask in #developers on IRC if you have any questions.

APPROVAL REQUIRED

All changes must meet the 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.
Patches nominated for aurora 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 aurora.
Approval requests will be processed by release drivers in the weekly Firefox/Channels meetings.
Set the appropriate status-firefoxN flag to "fixed" after landing a fix on the Aurora branch.

APPROVAL REQUIRED

All changes must meet the 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 release drivers in the weekly Firefox/Channels meetings.
Set the appropriate status-firefoxN flag to "fixed" after landing a fix on the Beta branch.

APPROVAL REQUIRED

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 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 release drivers.

APPROVAL REQUIRED

APPROVAL REQUIRED

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.

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

@@ Line 6: / Line 6: @@
 * '''<font color="orange">APPROVAL REQUIRED</font>''' because of {{bug|750661}}.
-** If your patch touches only files that are '''not part of the build on Windows''' then you have automatic approval to land.  In your commit message, use a=mac-only, a=linux-only, a=android-only, etc.
+** If your patch touches only files that are '''not part of the Windows libxul build''' then you have automatic approval to land.  In your commit message, use a=mac-only, a=android-only, a=js-only, a=chrome-only, a=npotb etc.
-** There's '''no official process in place yet''' for changes that are built on Windows.  Please stay tuned, or ask in #developers if you have a patch that really really needs to land.
+** If in doubt, please ask in #developers first!
 * '''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.
 * Set the ''Target Milestone'' field in Bugzilla to the current Nightly version after landing a bug fix on mozilla-central.