761
edits
User:Jprosevear/RapidReleaseUpdate: Difference between revisions
Jump to navigation
Jump to search
User:Jprosevear/RapidReleaseUpdate (view source)
Revision as of 15:49, 31 March 2011
, 31 March 2011no edit summary
Jprosevear (talk | contribs) |
Jprosevear (talk | contribs) No edit summary |
||
| Line 52: | Line 52: | ||
* there will be 3.6.x and 3.5.x releases and chemspill handling | * there will be 3.6.x and 3.5.x releases and chemspill handling | ||
= Current Discussions = | = Current Discussions = | ||
| Line 137: | Line 119: | ||
* Linux distribution that need to be prepared for speed of shipping | * Linux distribution that need to be prepared for speed of shipping | ||
* ATV outreach (screen readers, etc) | * ATV outreach (screen readers, etc) | ||
= Cheat Sheet = | |||
This is a list of key items that were discussed and are now at consensus or near-consensus. A Cliff Notes if you will of the key changes in the development process - '''refer to the documents in the Overview for all the details''' | |||
== Mini-Glossary == | |||
* '''Stabilization''' is the process of backing out and preff-ing off features and changes | |||
* '''Downstream Repository''' is the repository from which an antecedent or '''Upstream Repository''' is merged to, for instance mozilla-experimental is the downstream repository for mozilla-central in the current | |||
== Repositories == | |||
* mozilla-central merges to mozilla-experimental every 6 weeks | |||
* Stabilization occurs after the pull to the downstream branch | |||
* A bug fix for any repository (for instance mozilla-beta) lands in all upstream repositories at same time as well | |||
=== Feature & Major Change Policy === | |||
* All features and major changes should be kill switched and/or easy to back out | |||
* Where possible forward proofing should be employed (config, data) | |||
** at most backward and forward one version ie experimental vs mozilla-central | |||
* developer takes the pain of backing out! | |||