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.
Owned Areas
These are the directories and areas which are seen as "owned" by a particular comm-central application. The tree rules for each app apply to these directories and files.
Thunderbird
Thunderbird Rules affect these directories & areas in comm-central:
- Build Config (e.g. configure.in, build/, config/)
- directory/
- editor/
- mailnews/
- mail/
- other-licenses/*/thunderbird/
SeaMonkey
- suite/
- other-licenses/*/seamonkey/
Calendar
- calendar/
- other-licenses/*/sunbird/
comm-central (trunk) Rules
See above for which directories are owned by which application.
Thunderbird
When open: OPEN to all checkins following the checkin rules
Please ask on #maildev if you have questions.
SeaMonkey
When open: OPEN to all checkins following the checkin rules
Please ask on #seamonkey if you have questions.
Calendar
- 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.2 (branch) Rules
See above for which directories are owned by which application.
Thunderbird
- 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).
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.1 final release.
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
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).
Note: wanted and blocking bugs do not approve a patch for check in.
See Thunderbird/Thunderbird3_Security_And_Stability_Releases 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.