Yoga Release Schedule

Yoga 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.

06 October 2021 - 30 March 2022 (25 weeks)

Week

Cross-project events

Project-specific events

Oct 04 - Oct 08

Oct 11 - Oct 15

R-24

Oct 18 - Oct 22

R-23

Oct 25 - Oct 29

R-22

Nov 01 - Nov 05

R-21

Nov 08 - Nov 12

R-20

Nov 15 - Nov 19

R-19

Nov 22 - Nov 26

R-18

Nov 29 - Dec 03

R-17

Dec 06 - Dec 10

R-16

Dec 13 - Dec 17

R-15

Dec 20 - Dec 24

R-14

Dec 27 - Dec 31

R-13

Jan 03 - Jan 07

R-12

Jan 10 - Jan 14

R-11

Jan 17 - Jan 21

R-10

Jan 24 - Jan 28

R-9

Jan 31 - Feb 04

R-8

Feb 07 - Feb 11

R-7

Feb 14 - Feb 18

R-6

Feb 21 - Feb 25

R-5

Feb 28 - Mar 04

R-4

Mar 07 - Mar 11

R-3

Mar 14 - Mar 18

R-2

Mar 21 - Mar 25

R-1

Mar 28 - Mar 30

R+0

Subscribe to iCalendar file

Cross-project events

Yoga Goals Research

Pre-cycle planning and investigation into the community-wide goals for Yoga.

Virtual PTG

A virtual PTG will be held during this week (October 18-22, 2021). The Project Teams Gathering provides and opportunity for teams to collaborate and plan, and discuss requirements for future releases.

Yoga-1 milestone

18 November, 2021 is the Yoga-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 Xena deliverables by 16 December, 2021.

Yoga-2 milestone

06 January, 2022 is the Yoga-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 10 February, 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.

Yoga-3 milestone

24 February, 2022 is the Yoga-3 milestone. See project-specific notes for relevant deadlines.

Feature freeze

The Yoga-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 Yoga-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.

Yoga Community Goals Completed

Teams should prepare their documentation for completing the community-wide goals for Yoga.

RC1 target week

The week of 07 March, 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 21st-25th March, 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).

Yoga release

The Yoga coordinated release will happen on Wednesday, 30 March, 2022.

Open Infrastructure Summit

The Open Infrastructure Summit is expected to take place some time in October. Exact event dates are yet to be determined.

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.

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.

Manila

Manila Spec Freeze

All Manila specs targeted to Yoga 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.

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.