Mobile/Focus/Android/Train Schedule: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== Background ===
=== Background ===


Focus for Android will be moving to a bi-weekly cadence, so our releases will be schedule driven rather than dictated by feature development progress.  Both features and fixes will be allocated to the next available release upon completion. This will give us the ability to respond much more quickly to bug reports and user feedback.  
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.


While the release cadence will remain the same, the release numbering in this schedule is subject to change, as whether a release is classified as an X.0 depends on the significance of the features/enhancements being shipped.
=== Train Schedule - 2018 ===
 
As a further benefit, the process will be simpler and more predictable for the multiple teams involved, as all key milestones will recur on a bi-weekly basis as well. Also, the volume of work to test, translate, review etc... will be smaller for each release, allowing us to move much more quickly.
 
Releases with * indicate UX/feature-heavy releases.
 
=== Train Schedule - 2017 ===


{| class="wikitable" style="padding:10; font-size:100%; text-align:center;"
{| class="wikitable" style="padding:10; font-size:100%; text-align:center;"
|-
|-
| '''Version''' || '''Sprint Start''' || '''String Freeze/L10N Hand-off''' || '''Feature Complete''' || '''QA hand-off''' || '''QA & L10N App Sign-off''' || Legal Sign-off|| '''Submission''' || '''App Store Content Sign-off''' || '''Release''' || '''Release Themes'''
| '''Sprint''' || '''Sprint Start''' || '''Eng Complete''' || '''QA hand-off''' || '''QA Sign-off''' || '''Submission''' || '''Release''' || '''Release Version & Themes'''
|-
|-
| Aqua || July 24, 2017 || July 27, 2017 || Aug 4, 2017 || Aug 4, 2017 || Aug 10, 2017 || Aug 10, 2017 || Aug 11, 2017|| Aug 16, 2017  || Aug 17, 2017 || TBC
| Lavender || Jan 8, 2018 || Jan 21, 2018 || Jan 22,2018 || Jan 24, 2018 || Jan 25, 2018 || Upon Approval || V4.1 - Bug fixes
|-
|-
| Burgundy || Aug 7, 2017 || Aug 10, 2017 || Aug 18, 2017 || Aug 18, 2017 || Aug 24, 2017 || Aug 24, 2017 || Aug 25, 2017|| Aug 30, 2017  || Aug 31, 2017 || TBC
| Maroon || Jan 22, 2018 || Feb 4, 2018 || Feb 5, 2018 || Feb 7, 2018 || Feb 8, 2018 || Upon Approval || V4.2 - Bug Fixes
|-
|-
| Cobalt* || Aug 21, 2017 || Aug 24, 2017 || Sept 1, 2017 || Sept 1, 2017 || Sept 7, 2017 || Sept 7, 2017 || Sept 8, 2017|| Sept 20, 2017  || Sept 21, 2017 || TBC
| Navy || Feb 5, 2018 || Feb 18, 2018 || Feb 19, 2018 || Feb 21, 2018 || Feb 22, 2018 || Feb 27, 2018 || V5.0 - TBC
|-
|-
| Denim || Sept 4, 2017 || Sept 7, 2017 || Sept 15, 2017 || Sept 15, 2017 || Sept 21, 2017 || Sept 21, 2017 || Sept 22, 2017|| Sept 27, 2017 || Sept 28, 2017|| TBC
| Olive || Feb 19, 2018 || Mar 4, 2018 || Mar 5, 2018 || Mar 7, 2018 || Mar 8, 2017 || Upon Approval || V5.1 – Bug Fixes
|-
|-
| Ebony* || Sept 18, 2017 || Sept 21, 2017 || Sept 29, 2017 || Sept 29, 2017 || Oct 5, 2017 || Oct 5, 2017 ||  Oct 6, 2017|| Oct 11, 2017 || Oct 12, 2017 || TBC
| Plum || Mar 5, 2018 || Mar 18, 2018 || Mar 19, 2018 || Mar 21, 2018 || Mar 22, 2018 || Upon Approval || V5.2 – Bug Fixes
|-
|-
| Folly || Oct 2, 2017 || Oct 5, 2017 || Oct 13, 2017 || Oct 13, 2017 || Oct 19, 2017 || Oct 19, 2017 || Oct 20, 2017 || Oct 25, 2017 || Oct 26, 2017 || TBC
| Quartz-grey || Mar 19, 2018 || April 1, 2018 || April 2, 2018 || Apr 4, 2018 || Apr 5, 2018 || Apr 10, 2018 || V6.0 - TBC
|-
|-
| Granite* || Oct 16, 2017 || Oct 19, 2017 || Oct 27, 2017 || Oct 27, 2017 || Nov 2, 2017 || Nov 2, 2017 || Nov 3, 2017 || Nov 8, 2017 || Nov 9, 2017 || TBC
| Royal blue || Apr 2, 2018 || Apr 15, 2018 || Apr 16, 2018 || Apr 18, 2018 || Apr 19, 2018 || Upon Approval || V6.1 – Bug Fixes
|-
|-
| Harlequin || Oct 30, 2017 || Nov 2, 2017 || Nov 10, 2017 || Nov 10, 2017 || Nov 16, 2017 || Nov 16, 2017 || Nov 17, 2017 || Nov 22, 2017 || Nov 23, 2017 || TBC
| Seashell || Apr 16, 2018 || Apr 29, 2018 || Apr 30, 2018 || May 2, 2018 || May 3, 2018 || Upon Approval || V6.2 – Bug Fixes
|-
|-
| Indigo* || Nov 13, 2017 || Nov 16, 2017 || Nov 23, 2017 || Nov 23, 2017 || Nov 30, 2017 || Nov 30, 2017 || Dec 1, 2017 || Dec 6, 2017 || Dec 7, 2017 || TBC
| Teal || Apr 30 2018 || May 13, 2018 || May 14, 2018 || May 16, 2018 || May 17, 2018 || May 22, 2018 || V7.0 - TBC
|-
|-
| Jasmine || Nov 27, 2017 || Nov 30, 2017 || Dec 8, 2017 || Dec 8, 2017 || Dec 14, 2017 || Dec 14, 2017 || Dec 15, 2017 || Dec 20, 2017 || Dec 21, 2017 || 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''' -

Latest revision as of 23:12, 24 November 2017

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 -
Retrieved from "https://wiki.allizom.org/index.php?title=Mobile/Focus/Android/Train_Schedule&oldid=1184758"