Mobile/Focus/Android/Train Schedule

From MozillaWiki
Jump to: navigation, search

Background

Focus for iOS will be following a bi-weekly sprint cadence, so our releases will be schedule driven rather than dictated by feature development progress. This will give us the ability to respond much more quickly to bug reports and user feedback. Minor releases may be pushed at the end of any sprint as bug fixes and minor changes necessitate, while major releases are targeted following every 3rd sprint.

Train Schedule - 2018

Sprint Sprint Start Eng Complete QA hand-off QA Sign-off Submission Release Release Version & Themes
Lavender Jan 8, 2018 Jan 21, 2018 Jan 22,2018 Jan 24, 2018 Jan 25, 2018 Upon Approval V4.1 - Bug fixes
Maroon Jan 22, 2018 Feb 4, 2018 Feb 5, 2018 Feb 7, 2018 Feb 8, 2018 Upon Approval V4.2 - Bug Fixes
Navy Feb 5, 2018 Feb 18, 2018 Feb 19, 2018 Feb 21, 2018 Feb 22, 2018 Feb 27, 2018 V5.0 - TBC
Olive Feb 19, 2018 Mar 4, 2018 Mar 5, 2018 Mar 7, 2018 Mar 8, 2017 Upon Approval V5.1 – Bug Fixes
Plum Mar 5, 2018 Mar 18, 2018 Mar 19, 2018 Mar 21, 2018 Mar 22, 2018 Upon Approval V5.2 – Bug Fixes
Quartz-grey Mar 19, 2018 April 1, 2018 April 2, 2018 Apr 4, 2018 Apr 5, 2018 Apr 10, 2018 V6.0 - TBC
Royal blue Apr 2, 2018 Apr 15, 2018 Apr 16, 2018 Apr 18, 2018 Apr 19, 2018 Upon Approval V6.1 – Bug Fixes
Seashell Apr 16, 2018 Apr 29, 2018 Apr 30, 2018 May 2, 2018 May 3, 2018 Upon Approval V6.2 – Bug Fixes
Teal Apr 30 2018 May 13, 2018 May 14, 2018 May 16, 2018 May 17, 2018 May 22, 2018 V7.0 - TBC
Umber May 14, 2018 May 27, 2018 May 28, 2018 May 30, 2018 May 31, 2017 Upon Approval V7.1 – Bug Fixes
Violet May 28, 2018 June 10, 2018 June 11, 2018 June 13, 2018 - TBC June 14, 2018 - TBC TBC due to SFO All-Hands

Legend of Milestones

  • Sprint Start - Development work kicks off based on priorities identified, and commitments made in the last planning meeting, and continues for a period of two weeks.
  • QA hand-off - A first/potential candidate build is created by Engineering, and passed to QA for final Acceptance Testing. (This is required/performed in addition to the ongoing feature testing which takes place throughout the development cycle, as particular items land.)
  • QA Sign-off - Automated testing, as well as manual feature testing have been completed at a level determined to be sufficient for the release by QA. Any issues identified during acceptance testing, which were deemed to be blockers have been resolved, and the fixes verified by QA.
  • Submission -
  • Release -