Tree Rules/comm-central
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.
comm-central
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
When open: OPEN to all checkins following the checkin rules
Please ask on #maildev if you have questions.
SeaMonkey
Affected Areas
- suite/
- other-licenses/*/seamonkey/
Current Rules
When open: OPEN to all checkins following the checkin rules
Please ask on #seamonkey if you have questions.
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.
Please ask on #calendar if you have questions.
comm-1.9.1
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 release candidates.
- Checkins are allowed only if:
- Strings in mail/locales and editor/ui are not affected.
- The patch has approval-thunderbird3.0.1+
Note: wanted and blocking bugs do not approve a patch for check in.
Patches for approval must:
- Not affect strings in mail/locales and editor/ui.
- Land on trunk before requesting approval. Preferably to have some time baking before approval is requested.
- Be accompanied by a risk assessment as to the risk the patch poses and the reason we need to take it for the 3.0.* security releases when the approval is requested.
Patches are unlikely to be accepted if:
- They are not affecting security or stability (in the first couple of point releases this may be relaxed by drivers if there are fixes for significant regressions).
- They are high risk.
- They have no tests (some patches may be accepted without tests if there is a good reason why there aren't any, and if they can be demonstrated to be well-tested, if you need support for writing tests, please ask in #maildev).
Please ask on #maildev if you have questions.
SeaMonkey
Affected Areas
- suite/
- other-licenses/*/seamonkey/
Current Rules
- 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
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.
Please ask on #calendar if you have questions.