== [http://tbpl.mozilla.org/ mozilla-central] (Nightly channel) ==
* '''<font color="orange">APPROVAL REQUIRED</font> until April 24''' to help stabilize [[Fennec/NativeUI]]. See the [https://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/b5647a8a62032a73 discussion thread] for context.
** Bugs with '''blocking-fennec1.0''' (except "soft" blockers) can land with a=blocking-fennec.
** Buth with '''tracking-firefoxN+''' can land with a=tracking-firefox.
** Bugs whose whiteboard contains either '''sg:high''', or '''sg:crit''' can land with a=security.
** Changes that are '''not part of the Native Fennec build''' also have blanket approval to land. This includes:
*** Test-only changes (a=test-only)
*** Desktop-only or platform-specific changes (a=desktop-only, a=windows-only, a=b2g-only, etc.). This only covers patches that touch browser/*, widget/windows, widget/gtk2 or widget/cocoa at the Mobile Team's request.
*** Changes that are not part of any build (a=npotb).
** For all other changes, use the '''approval-mozilla-central?''' flag to request approval, and leave a comment with the reasons for your request. Release drivers will decide which bugs are sufficiently low-risk and/or time-sensitive.
** '''Non-approved changes''' can land on the [http://hg.mozilla.org/projects/birch/ Birch project branch], which will follow the same process as mozilla-inbound except that changes will not be pushed to mozilla-central until after April 24.
* '''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.
