Zed Release Schedule

Zed Release Schedule

Note

Deadlines are generally the Thursday of the week on which they are noted below. Exceptions to this policy will be explicitly mentioned in the event description.

30 March 2022 - 05 October 2022 (27 weeks)

Week

Cross-project events

Project-specific events

Mar 28 - Apr 01

Apr 04 - Apr 08

R-26

Apr 11 - Apr 15

R-25

Apr 18 - Apr 22

R-24

Apr 25 - Apr 29

R-23

May 02 - May 06

R-22

May 09 - May 13

R-21

May 16 - May 20

R-20

May 23 - May 27

R-19

May 30 - Jun 03

R-18

Jun 06 - Jun 10

R-17

Jun 13 - Jun 17

R-16

Jun 20 - Jun 24

R-15

Jun 27 - Jul 01

R-14

Jul 04 - Jul 08

R-13

Jul 11 - Jul 15

R-12

Jul 18 - Jul 22

R-11

Jul 25 - Jul 29

R-10

Aug 01 - Aug 05

R-9

Aug 08 - Aug 12

R-8

Aug 15 - Aug 19

R-7

Aug 22 - Aug 26

R-6

Aug 29 - Sep 02

R-5

Sep 05 - Sep 09

R-4

Sep 12 - Sep 16

R-3

Sep 19 - Sep 23

R-2

Sep 26 - Sep 30

R-1

Oct 03 - Oct 07

R+0

Subscribe to iCalendar file

Cross-project events

Virtual PTG

A virtual PTG will be held during this week (April 04-08, 2022). The Project Teams Gathering provides an opportunity for teams to collaborate and plan, and discuss requirements for future releases.

Zed-1 milestone

19 May, 2022 is the Zed-1 milestone. See project-specific notes for relevant deadlines.

Yoga Cycle-Trailing Release Deadline

All projects following the cycle-trailing release model must release their Yoga deliverables by 23 June, 2022.

Zed-2 milestone

14 July, 2022 is the Zed-2 milestone. See project-specific notes for relevant deadlines.

Membership Freeze

Projects must participate in at least two milestones in order to be considered part of the release. Projects made official after the second milestone, or which fail to produce milestone releases for at least one of the first and second milestones as well as the third milestone, are therefore not considered part of the release for the cycle. This does not apply to cycle-trailing packaging / lifecycle management projects.

Extra-ATC freeze

All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. That allow teams to list active contributors to their projects and who do not have a code contribution this cycle, and therefore won’t automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml before the Extra-ATC freeze on 18 August, 2022.

Final release for non-client libraries

Libraries that are not client libraries (Oslo and others) should issue their final release during this week. That allows to give time for last-minute changes before feature freeze.

Zed-3 milestone

01 September, 2022 is the Zed-3 milestone. See project-specific notes for relevant deadlines.

Feature freeze

The Zed-3 milestone marks feature freeze for projects following the release:cycle-with-rc model. No featureful patch should be landed after this point. Exceptions may be granted by the project PTL.

Final release for client libraries

Client libraries should issue their final release during this week, to match feature freeze.

Soft StringFreeze

You are no longer allowed to accept proposed changes containing modifications in user-facing strings. Such changes should be rejected by the review team and postponed until the next series development opens (which should happen when RC1 is published).

Requirements freeze

After the Zed-3 milestone, only critical requirements and constraints changes will be allowed. Freezing our requirements list gives packagers downstream an opportunity to catch up and prepare packages for everything necessary for distributions of the upcoming release. The requirements remain frozen until the stable branches are created, with the release candidates.

RC1 target week

The week of 12 September, 2022 is the target date for projects following the release:cycle-with-rc model to issue their first release candidate.

Hard StringFreeze

This happens when the RC1 for the project is tagged. At this point, ideally no strings are changed (or added, or removed), to give translators time to finish up their efforts.

Final RCs and intermediary releases

The week of 26th - 30th September, 2022 is the last week to issue release candidates or intermediary releases before release week. During release week, only final-release-critical releases will be accepted (at the discretion of the release team).

Zed release

The Zed coordinated release will happen on Wednesday, 05 October, 2022.

Open Infrastructure Summit

The Open Infrastructure Summit happens in this week, 7th - 9th June, 2022 in Berlin, Germany. See details at the official OpenInfra Summit Page.

Cycle Highlights

Cycle highlights need to be added to the release deliverables by feature freeze to be included in any marketing release messaging. Highlights may be added after this point, but they will likely only be useful for historical purposes.

See the Project Team Guide for more details and instructions on adding these highlights.

For examples of previous release highlights: Stein Highlights, Train Highlights, Ussuri Highlights, Victoria Highlights. Wallaby Highlights. Xena Highlights. Yoga Highlights.

Project-specific events

Oslo

Oslo Feature Freeze

All new Oslo features must be proposed and substantially complete, with unit tests by the end of the week.

Cinder

Cinder Mid Cycle PTG - 1

We will be conducting a mid-cycle PTG on 1st June (Wednesday) which is a continuation of Zed PTG to track progress and discuss topics in a similar manner as of PTG.

Wednesday 01 June 2022 (1400-1600 UTC).

Cinder Spec Freeze

All Cinder Specs for features to be implemented in Zed must be approved by Friday 24 Jun 2022 (23:59 UTC).

Cinder New Driver Merge Deadline

The deadline for merging a new backend driver to Cinder for the Zed release is Friday 15 July 2022 (23:59 UTC) which is the same as Milestone 2. New drivers must be (a) code complete including unit tests, (b) merged into the code repository, and (c) must have a 3rd Party CI running reliably.

Cinder New Target Driver Merge Deadline

The deadline for merging a new target driver to Cinder for the Zed release is Friday 15 July 2022 (23:59 UTC) which is the same as Milestone 2. New target drivers must be (a) code complete including unit tests, (b) merged into the code repository, and (c) must have a 3rd Party CI running reliably.

Cinder New Feature Status Checkpoint

If your new Cinder feature requires client support, keep in mind that the final release for client libraries is in four weeks. Thus your Cinder feature should be substantially complete with unit tests by this time so that any client changes can be reviewed, tested, and merged before 02 September 2022.

Cinder Driver Features Declaration

New features added to Cinder drivers must be merged at the time of the OpenStack-wide Feature Freeze, which is coming up in three weeks. Before the Cinder meeting this week, you should post a blueprint in Launchpad listing the Gerrit reviews of features you’d like to land in Zed. (You can look among the Yoga and Xena blueprints for examples; contact the PTL if you have any questions.) This will help the team prioritize reviews and give you candid early feedback on whether the features look ready.

Cinder 3rd Party CI Compliance Checkpoint

This is a reminder that in order for a Cinder driver to be considered ‘supported’ in the Zed release, its third party CI must be running properly when the Cinder team does a final compliance check around the time of the third milestone. See the Driver Compliance section of the Cinder Documentation for details.

Manila

Manila Spec Freeze

All Manila specs targeted to Zed must be approved by the end of the week.

Manila New Driver Deadline

By the end of the week all new backend drivers for Manila must be substantially complete, with unit tests, and passing 3rd party CI. Drivers do not have to actually merge until feature freeze.

Manila Feature Proposal Freeze

All new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week.

Manila Bugsquash

Manila community event promoted in order to fast-track the closure of bugs.

Manila Hackathon

Manila community event promoted in order to tackle the implementation of features or tech debt areas.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.