Firefox/Windows10: Difference between revisions

No edit summary
Line 50: Line 50:
*[https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates Firefox main release schedule] is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.
*[https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates Firefox main release schedule] is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.


==Themes==
==Priorities==
*These are the high level areas of focus to make sure Product, UX, and Engineering are aligned. 
* P1 bug list (target=40)
*Many Themes are what we then break down into User Stories, though some are more work based groupings like "quality" or "tech-debt". 
* P2 bug list (target=41)
*This is not a commitment to the next projects - just our scratch area of order of relative priority. 
* P3 bug list (target=42)
*As new requests or needs come in - they are evaluated in where they fit in the relative list.
Example Theme list:
*finishing Theme 1 (large change)
*Theme 2: any time constraints/dependencies.  [theme] or [meta] bug number link is ideal
*Theme 3: quick why and bug number
Things we want to do - but parking lot until higher priorities are done:
*Process Improvement: Theme
*Other platform Investigation
*Tech-debt: any time constraints/dependencies
*Theme 4
*Quality: description of areas
*Theme 5
'''Risks'''
*Risk 1 : ex: Roadmap goals for the release in November are too high for ____(dev, UX, PM?) resources by x amount (bugs? points? UX resources).  likely will not make any features beyond x, y, z.
*Risk 2 : ex: Dependency on a service that is not established/planned for from another team.  Need help prioritizing if we should delay the feature in this project or raise the priority in the other team based on their existing backlog


==Current==
==Current==
Confirmed users
2,492

edits