User:Jchaulk/Desktop Roadmap Draft
From MozillaWiki
Last updated: 2014/08/12
Roadmap
Firefox 31 (Released)
Schedule
-
Nightly: Mar 17, 2014
-
Aurora: April 29, 2014
-
Beta: June 10, 2014
- Release: Jul 22, 2014
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Firefox 32 (Beta)
Schedule
-
Nightly: Apr 28, 2014
-
Aurora: June 10, 2014
- Beta: July 22 2014
- Release: Sep 2, 2014
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Firefox 33 (Aurora)
Schedule
-
Nightly: Jun 9, 2014
- Aurora: July 22, 2014
- Beta: Sept 2, 2014
- Release: Oct 14, 2014
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Firefox 34 (Nightly)
Schedule
- Nightly: Jul 21, 2014
- Aurora: Sept 2, 2014
- Beta: Oct 14, 2014
- Release: Nov 25, 2014
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Firefox 35
Schedule
- Nightly: Sept 2, 2014
- Aurora: Oct 14, 2014
- Beta: Nov 24, 2014
- Release: Jan 6, 2014
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Firefox 36
Schedule
- Nightly: Oct 14, 2014
- Aurora: Nov 24, 2014
- Beta: Jan 5, 2015
- Release: Feb 17, 2015
- [[ | Check QA Status ]]
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Product Backlog Items Not Yet Assigned to a Release
P1
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
P2
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
P3
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
P* - TO BE PRIORITIZED
| Px
|
Status
|
Project
|
Theme*
|
Epic
|
|
|
|
|
|
|
Legend
Theme tags
- ST - Search Test
- LP - Loop
- ORG - Organic Search
- TRN - Translation
- SD - Search Diversion
- IPP - In Product Promotion
- TL - Tiles
- 3PC - 3rd Party Cookes
- EME - EME
- REG - Regressions
- CRS - Crashers
- ATO - Autocomplete
- TEL - Telemetry
- FHR - Fx Health Report
Status tags
- [ON TRACK] - {{mok}} - actively being worked on and those assigned feel comfortable and confident in achieving the target milestone.
- [PLANNED] - {{mplan}} - feature has resources identified and assigned, work is adequately scoped out and engineering agrees that enough information is available to get the work started. Resources are identified and assigned, but work may not have commenced.
- [PROPOSED] - {{mprop}} - feature is defined to an adequate degree for engineering to assess that they have the resources that can address the feature for the targeted release. Resources can be identified, but work has not commenced.
- [AT RISK] - {{mrisk}} - blocking bug / high number of bugs / other confidence-shakers makes us feel that a feature may not achieve the targeted milestone.
- [IN PROGRESS] - {{mprog}} - actively being worked on but not yet mature enough to be committed to a specific release
- [INVESTIGATION NEEDED] - {{minvest}} - development investigation needed to move forward
