Tree Rules/comm-central: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 18: Line 18:
* Thunderbird is code frozen in preparation for the 3.0 Beta 4 release..
* Thunderbird is code frozen in preparation for the 3.0 Beta 4 release..
* Checkins are allowed only if:
* Checkins are allowed only if:
** The patch has ''approval-thunderbird3.0+'' from the release driver - Mark Banner (aka standard8).
** The patch has ''approval-thunderbird3.0+''
** The patch does not affect strings in mail/locales or editor/ui/locales
** The patch is on a bug marked as ''blocking-thunderbird3.0+''


Note: ''wanted-thunderbird3.0+'' does '''not''' approve a patch for check in.
Note: ''wanted-thunderbird3.0+'' does '''not''' approve a patch for check in.


<!--
When requesting approval, please state the (stability) risk this patch poses and the reason we need to take it for the 3.0 release.
When requesting approval, please state the (stability) risk this patch poses and the reason we need to take it for the 3.0 Beta 4 release.


Patches that are tidy up only or high risk will most likely be rejected.
Patches that are tidy up only or high risk will most likely be rejected.
-->


== SeaMonkey ==
== SeaMonkey ==

Revision as of 08:55, 16 September 2009

Due to multiple applications using comm-central different parts of comm-central can have different rules at different times. We try to keep these as simple as possible, if in doubt, please ask on irc.

Thunderbird

Affected Areas

Thunderbird Rules affect these directories & areas in comm-central:

  • Build Config (e.g. configure.in, build/, config/)
  • directory/
  • editor/
  • mailnews/
  • mail/
  • other-licenses/*/thunderbird/

Current Rules

  • Thunderbird is code frozen in preparation for the 3.0 Beta 4 release..
  • Checkins are allowed only if:
    • The patch has approval-thunderbird3.0+
    • The patch is on a bug marked as blocking-thunderbird3.0+

Note: wanted-thunderbird3.0+ does not approve a patch for check in.

When requesting approval, please state the (stability) risk this patch poses and the reason we need to take it for the 3.0 release.

Patches that are tidy up only or high risk will most likely be rejected.

SeaMonkey

Affected Areas

  • suite/
  • other-licenses/*/seamonkey/

Current Rules

  • SeaMonkey is feature frozen in preparation for the 2.0 release.. No new features allowed.
  • Checkins are allowed only if:
    • The bug is marked as wanted-seamonkey2.0+ or blocking-seamonkey2.0+
    • The patch has approval-seamonkey2.0+

When requesting approval, please state the (stability) risk this patch poses and the reason we need to take it for the 2.0 release.

Calendar

Affected Areas

  • calendar/
  • other-licenses/*/sunbird/

Current Rules

  • Calendar strings are frozen for the 1.0 beta 1 release.
    • No changes to strings are allowed.