Tree Rules/comm-central: Difference between revisions

Jump to navigation Jump to search
Line 62: Line 62:
Note: wanted and blocking bugs do '''not''' approve a patch for check in.
Note: wanted and blocking bugs do '''not''' approve a patch for check in.


Patches for approval must:
See [[Thunderbird/Landing_Patches_on_Thunderbird3.1]] for more information about getting approval for landing patches for Thunderbird 3.1.
 
* 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 ===
=== SeaMonkey ===
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits

Navigation menu