Tree Rules

For comm-central tree rules, see this page.

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

mozilla-central (Nightly channel)

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