User:Jprosevear/RapidReleaseUpdate
Overview
The Mozilla project's plan is is to introduce much faster releases provide regular improvements faster to users without disrupting longer term work.
A draft for the high level proposal of this process is at: http://people.mozilla.com/~sayrer/2011/temp/process.html
A detailed process plan is being worked on by Christian and Sheila. [need ETA]
The next checkpoint for discussing this process and its evolution will be March 29 in the platform/development meeting
Current State and Decisions
The following is a list consisting of items in a steady state for this process or decisions that have been made and generally agreed on in the project.
mozilla-central
- open for a 3 week period starting March 23 and ending April 13
- build sheriffing will [link to bsmedberg's mail?] focus on high gain, low risk items
- cedar is being run by Ehsan and is available for pre-mozilla-central landing
- the focus so far here is on patches with approval for 2.0 [check this]
+ features and major changes must be + kill switched or easy to back out + forward proofed (config, data) + dev takes the pain of backing out!
Version Numbering
- version number of 2.2a1pre/4.2a1pre
- AMO people request there is better planning around versions [need cite]
User Agent
- nothing other than 5.0 versioning for mc/dev/beta
Nightlies & Beta Channel
- Nightlies stay on mozilla-central
- Beta users stay on beta channel with no updates
- This may change in future with audience partitioning
4.0.x
- there will be 4.0.x releases and chemspill handling