761
edits
User:Jprosevear/RapidReleaseUpdate: Difference between revisions
User:Jprosevear/RapidReleaseUpdate (view source)
Revision as of 14:03, 31 March 2011
, 31 March 2011→Current State and Decisions
Jprosevear (talk | contribs) No edit summary |
Jprosevear (talk | contribs) |
||
| Line 15: | Line 15: | ||
https://lists.mozilla.org/listinfo/dev-planning | https://lists.mozilla.org/listinfo/dev-planning | ||
== | == Firefox 5 State == | ||
This is a list of actions that have been taken for FF5. Differences or potential differences due to ongoing discussions in future releases (post FF6 and beyond) will be noted. | |||
=== mozilla-central === | === mozilla-central === | ||
* open for a 3 week period starting March 23 and ending April 12 | * open for a 3 week period starting March 23 and ending April 12 | ||
* | ** NOTE: will 6 weeks in future releases | ||
* build sheriffing will focus on high gain, low risk items | * build sheriffing will focus on high gain, low risk items | ||
** bsmedberg | ** see bsmedberg for questions | ||
** tree is closed when there is no sheriff | ** tree is closed when there is no sheriff | ||
* cedar | * cedar is being run by Ehsan and is being used for checking-needed bugs | ||
=== Version and User Agent === | |||
* version number of 2.2a1pre/4.2a1pre | |||
** NOTE: Versioning under discussion | |||
* historical user agent string, ie | |||
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110330 Firefox/4.2a1pre | |||
** NOTE: Changes to user agent string under discussion | |||
=== Bugzilla === | |||
* mozilla2.2 target milestone for mozilla-central | |||
** NOTE: May change do to version number changes and/or triage process changes that are in discussion | |||
=== Nightlies & Beta Channel === | |||
* Nightlies stay on mozilla-central | |||
* Beta users stay on beta channel with no updates | |||
** NOTE: This will change either with progress on 4.0.1 or with channel discussion finishing | |||
== 4.0.x and Previous Releases == | |||
This section clarifies some questions that have come up about the relationship between | |||
* 5.0 and newer processes will not be "backported" onto 4.0.x and older releases | |||
* there will be 4.0.x releases and chemspill handling | |||
** branch team is taking over for 4.0.1 | |||
* there will be 3.6.x and 3.5.x releases and chemspill handling | |||
== Blah == | |||
=== Branch pulling === | === Branch pulling === | ||
* stabilize after pull to downstream branch (ie post mozilla-central to mozilla-experimental) | * stabilize after pull to downstream branch (ie post mozilla-central to mozilla-experimental) | ||
** avoid closing upstream branch (ie m-c) during stabilization | ** avoid closing upstream branch (ie m-c) during stabilization | ||
** AMO people request there is better planning around versions | |||
*** From fligtar: it's a hassle for AMO and probably others (metrics, SUMO, socorro?) when we create versions like this that will eventually have to be manually mapped to other versions (3.1 => 3.5, 3.7 => 4.0). And the Compatibility Reporter was ready to go for 5.0a1pre builds and we're now having to rush a version to support 4.2. Plus, it just adds confusion for add-on developers and everyone else who thought Firefox 5 is coming next. Our version system is complicated enough; we really shouldn't do things like this to make it worse. | |||
=== Feature & Major Change Policy === | === Feature & Major Change Policy === | ||
| Line 40: | Line 68: | ||
* how does a bug fix for firefox-beta land | * how does a bug fix for firefox-beta land | ||
** it lands in all places (m-c, experimental, beta) | ** it lands in all places (m-c, experimental, beta) | ||
== In Progress Actions, Unresolved Decisions and Their Owners == | == In Progress Actions, Unresolved Decisions and Their Owners == | ||