Tree Rules/comm-central: Difference between revisions

Jump to navigation Jump to search

Tree Rules/comm-central (view source)

Revision as of 09:26, 27 April 2012

600 bytes added ,  27 April 2012
no edit summary
No edit summary
No edit summary
Line 27: Line 27:
* other-licenses/*/sunbird/
* other-licenses/*/sunbird/


== comm-central (trunk) Rules ==
== comm-central (Nightly channel) ==


See above for which directories are owned by which application.
* '''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 comm-central.
* Please ask the sheriff channel (typically, #maildev, #seamonkey or #calendar depending on the application you are landing to) on [[IRC]] if you have questions.


=== Thunderbird ===
== comm-aurora ==


'''When open: <font color="green">OPEN</font>''' to all checkins following the [https://developer.mozilla.org/en/comm-central#comm-central_tree_rules checkin rules]
'''<font color="orange">APPROVAL REQUIRED</font>'''


Please ask on #maildev if you have questions.
* '''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.
* Patches must have the '''approval-comm-aurora+''' flag in Bugzilla. To request approval, set the approval-comm-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 comm-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 are processed regularly.
* Set the appropriate ''status-thunderbirdN'', ''status-seamonkeyN'' flag to "fixed" after landing a fix on the Aurora branch.


=== SeaMonkey ===
== comm-beta ==


'''When open: <font color="green">OPEN</font>''' to all checkins following the [https://developer.mozilla.org/en/comm-central#comm-central_tree_rules checkin rules]
'''<font color="orange">APPROVAL REQUIRED</font>'''


Please ask on #seamonkey if you have questions.
* '''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.
* Patches must have the '''approval-comm-beta+''' flag in Bugzilla. To request approval, set the approval-comm-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 are processed regularly.
* Set the appropriate ''status-thunderbirdN'', ''status-seamonkeyN'' flag to "fixed" after landing a fix on the Beta branch.


=== Calendar ===
== comm-release ==


* Calendar strings are frozen for the 1.0 beta 1 release.
'''<font color="orange">APPROVAL REQUIRED</font>'''
** No changes to strings are allowed.


Please ask on #calendar if you have questions.
* Patches must have the '''approval-comm-release+''' flag in Bugzilla. To request approval, set the approval-comm-release? flag on the patch you wish to check in.
* In the normal development process, no changes will land on comm-release except [[RapidRelease/Calendar|regular merges from comm-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 the [Releases/Drivers release drivers for the appropriate product].


== comm-1.9.2 (branch) Rules ==
== comm-esr10 (Thunderbird 10.0.x ESR) ==


See above for which directories are owned by which application.
'''<font color="orange">APPROVAL REQUIRED</font>'''


=== Thunderbird ===
* We use the same process as the Firefox [[Release Management/ESR Landing Process]].
 
** Use the tracking-thunderbird-esr10 and status-thunderbird-esr10 flags instead of the Firefox ones.
* Thunderbird is string and feature frozen in preparation for the 3.1 release candidates.
* Checkins are allowed only if:
** Strings in mail/locales and editor/ui are '''not''' affected.
** The patch has ''approval-thunderbird3.1+'' (where 'x' is the number of the next release) or the bug has ''blocking-thunderbird3.1'' set to a '+' value.
** The patch '''is not''' on a bug which has already been resolved as fixed for a Thunderbird 3.1 release.
 
Note: wanted bugs do '''not''' approve a patch for check in.
 
See [[Thunderbird/Security_And_Stability_Releases/Rules]] for more information about getting approval for landing patches for Thunderbird 3.1.
 
=== SeaMonkey ===
 
N/A - SeaMonkey does not participate on the 1.9.2 branch.
 
=== Calendar ===
 
TBD.
 
== comm-1.9.1 (branch) Rules ==
 
See above for which directories are owned by which application.
 
=== Thunderbird ===
 
* Thunderbird is code frozen in preparation for the 3.0 release candidates.
* Checkins are allowed only if:
** Strings in mail/locales and editor/ui are '''not''' affected.
** The patch has ''approval-thunderbird3.0.x+'' (where 'x' is the number of the next release).
** The patch '''is not''' on a bug which has already been resolved as fixed for a Thunderbird 3.0 release.
 
Note: wanted and blocking bugs do '''not''' approve a patch for check in.
 
See [[Thunderbird/Security_And_Stability_Releases/Rules]] for more information about requirements for getting approval to landing patches.
 
=== SeaMonkey ===
 
* SeaMonkey on comm-1.9.1 is restricted to security, stability and polish fixes in the 2.0.x series
* Checkins are allowed only if:
** The patch has explicit ''approval-seamonkey2.0.x+'' where x is the next upcoming non-tagged stability update.
 
When requesting approval, please state the (stability) risk this patch poses and the reason we need to take it for the 2.0 series.
 
Please ask on #seamonkey if you have questions.
 
=== Calendar ===
 
There is no active development on the comm-1.9.1 branch for Calendar.
Standard8
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/424914"

Navigation menu