Tree Control Level: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
(Tree Control Level (Threat Level) descriptions) |
m (development category) |
||
| Line 26: | Line 26: | ||
* Typical trunk development will be at level 0. Once a deadline/featureset is determined for the next milestone release, it will move to level 1. A few weeks before release, it will move to level 2 and eventually level 3 immediately before release. In the case of major (beta/production) releases, the amount of time spent in the higher levels will be longer. | * Typical trunk development will be at level 0. Once a deadline/featureset is determined for the next milestone release, it will move to level 1. A few weeks before release, it will move to level 2 and eventually level 3 immediately before release. In the case of major (beta/production) releases, the amount of time spent in the higher levels will be longer. | ||
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/f569a23ce266a451/265344ae5291dee0 Developer discussion] | * [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/f569a23ce266a451/265344ae5291dee0 Developer discussion] | ||
[[Category:Development]] | |||
Latest revision as of 17:31, 4 October 2007
Throughout the development process, varying levels of restriction are placed on making code changes to the Mozilla development tree. The Tree Control Level (aka Threat Level) indicates these restrictions.
Tree Control Level
| Level | Color | Description |
|---|---|---|
| Level 0 | Green | Open tree. Checkin after r+/sr+ only. |
| Level 1 | Yellow | "x.x+" and "wanted-x.x" bugs auto-approved. Other changes require explicit approval flags. |
| Level 2 | Orange | "x.x+" bugs auto-approved. Other changes require explicit approval flags. |
| Level 3 | Red | All check-ins require explicit approval flags prior to check-in. |
Notes
- Code changes are for the tree as a whole, but specific components within the tree may have different restrictions.
- Typical trunk development will be at level 0. Once a deadline/featureset is determined for the next milestone release, it will move to level 1. A few weeks before release, it will move to level 2 and eventually level 3 immediately before release. In the case of major (beta/production) releases, the amount of time spent in the higher levels will be longer.
- Developer discussion
