List view
For tasks/issues/bugs that are not required for our near-term milestones, we will tag these accordingly so we can keep track of them.
No due date•11/18 issues closed- No due date•6/7 issues closed
The purpose of Milestone 4 is to deliver the first Beta build. The work here is defined as 'feature complete' which focuses on delivering against all the Core Apps defined in the B2G product roadmap. Completed features should functionally work against the specific app requirements and UX specs/visual designs should be implemented at the end of this milestone. Bugs are expected and can be the focused for Beta 2, but core functionality and UX details should be implemented. The goal is to land all P1 bugs for the Beta 1 milestone as well as any outstanding P1 tasks from Alpha. Wiki tracking specific features/tasks:: To be created shortly.
Overdue by 13 year(s)•Due by June 29, 2012•65/67 issues closedThe purpose of Milestone 3 is to deliver an Alpha build. The work here is defined as 'functional complete' which primarily is focused on ensuring all Gecko work/APIs have been proposed, specified and implemented. In addition, there is a prioritized product backlog with Core Apps that the Gaia team will be working towards in M3 and M4 (Beta 1). The goal is to land all P1 bugs listed below for the Alpha milestone as well as any outstanding P1 tasks from M2.5. Wiki tracking specific features/tasks:: https://wiki.mozilla.org/B2G/Schedule_Roadmap/M3
Overdue by 13 year(s)•Due by June 1, 2012•207/210 issues closed