Program Management

To see larger versions of the images below, right-click on them and open them in a separate browser tab or window.

Schedule

Schedule Milestones

The following graphic shows the timeline of phases and milestones associated with each release:

This shows how the phases and milestones of one release overlap with those of the next release:

Milestone Definitions

Milestone	Also Called	Definition
P0	Planning Kickoff	Identify key features and track them in release plan
P1		TSC Agrees on Major Features and Schedule
M0	Merge Window Open	All features, Sized, and Assigned Merge Window Is Opened
M1	M1 Checkpoint	Major Features Ready for Code Reviews Test Plans Reviewed and Approved
M2	Feature Merge Window Close	Feature Freeze Feature Development Complete (including Code Reviews and Unit Tests Passing) Features per release plan Implemented Feature Merge Window Is Closed Test Development Complete Technical Documentation Created/Updated and Ready for Review CCB Control Starts
M3	Code Freeze	Code Freeze Final RC Tagged and Built
M4	Release	TSC Reviews the Release Criteria Report and Approves Release Release Tagged Make the Release

Actual and planned milestone dates

Version	2.5	2.6	2.7 (LTS2)	3.0	3.1
M0	2020/09/27
M1	2021/12/11
M2	2021/01/22	2021/05/07	2021/08/27	2022/01/18	2022/05/20
M3	2021/02/05	2021/05/21	2021/10/08	2022/02/04	2022/06/03
M4	2021/02/12	2021/06/04	2021/10/15	2022/02/11	2022/06/10

2.7 Release (LTS) Details:

• Feature Freeze: August 27th, 2021
• main branch opens for 3.0 development: September 24th, 2021
• Code Freeze: October 8th, 2021
• Release Date: October 15th, 2021

3.0 Release:

• Master open for 3.0: September 24th
• Release Date: February 11th, 2022

In italic, actual schedule.

Note, as per the TSC F2F of 2019/10/31, releases after and including 2.4 have a 4 month cadence.
The figures above still reflect a 3 month cadence which applies until and including release 2.3.

Past releases' schedules

Version	1.11	1.12	1.13	1.14	2.0	2.1	2.2	2.3	2.4
P0	2017/09/20	2017/12/27	2018/03/21	2018/06/27	2019/02/08	2019/06/28	2019/09/20	2019/12/20	2020/03/20
P1	2017/10/11	2018/01/10	2018/04/11	2018/07/18	2019/03/01	2019/07/19	2019/10/11	2020/01/10	2020/04/10
M0	2017/11/29	2018/02/28	2018/05/30	2018/09/05	2019/04/16	2019/09/06	2019/12/09	2020/03/10	2020/06/05
M1	2017/12/27	2018/03/21	2018/06/20	2018/09/26	2019/05/31	2019/10/11	2020/01/10	2020/04/10	2020/08/07
M2	2018/01/10	2018/04/11	2018/08/11	2019/02/08	2019/08/11	2019/11/10	2020/02/08	2020/05/08	2020/09/05
M3	2018/03/02	2018/05/23	2018/08/29	2019/03/15	2019/09/03	2019/12/03	2020/02/29	2020/05/22	2020/09/24
M4	2018/03/09	2018/05/30	2018/09/05	2019/04/16	2019/09/06	2019/12/09	2020/03/10	2020/05/29	2020/09/27

Schedule Details

For more details about the project phases, milestones, etc. see More Schedule Details

TSC In-Meeting Voting

For items requesting an in-meeting vote of the Zephyr Technical Steering Committee (TSC), assuming quorum requirements have been met, the default voting mechanism will be a verbal motion to determine if there is general consensus. If there are no objections to a motion being brought forward, general consensus is assumed and the motion passes. Should there be any objections raised, the vote will move to email, and be executed using the Voting Guidelines outlined in Section 8 of the Project Charter.

Should a motion be deemed urgent by the TSC Chair, and assuming quorum requirements have been met, the Chair may call for a roll call vote in-meeting.