Ussuri Release Schedule

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

21 October 2019 - 15 May 2020 (30 weeks)

Week

Cross-project events

Project-specific events

Oct 14 - Oct 28

Oct 21 - Oct 25

R-29

Oct 28 - Nov 01

R-28

Nov 04 - Nov 08

R-27

Nov 11 - Nov 15

R-26

Nov 18 - Nov 22

R-25

Nov 25 - Nov 29

R-24

Dec 02 - Dec 06

R-23

Dec 09 - Dec 13

R-22

Dec 16 - Dec 20

R-21

Dec 23 - Dec 27

R-20

Dec 30 - Jan 03

R-19

Jan 06 - Jan 10

R-18

Jan 13 - Jan 17

R-17

Jan 20 - Jan 24

R-16

Jan 27 - Jan 31

R-15

Feb 03 - Feb 07

R-14

Feb 10 - Feb 14

R-13

Feb 17 - Feb 21

R-12

Feb 24 - Feb 28

R-11

Mar 02 - Mar 06

R-10

Mar 09 - Mar 13

R-9

Mar 16 - Mar 20

R-8

Mar 23 - Mar 27

R-7

Mar 30 - Apr 03

R-6

Apr 06 - Apr 10

R-5

Apr 13 - Apr 17

R-4

Apr 20 - Apr 24

R-3

Apr 27 - May 01

R-2

May 04 - May 08

R-1

May 11 - May 15

R-0

Subscribe to iCalendar file

Cross-project events

Ussuri Goals Research

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

Open Infrastructure Summit

The Open Infrastructure Summit happens during this week in Shanghai, China. It will include a “Forum” in which people from all parts of our community will gather to give feedback on the last release (Train) and discuss requirements for future releases.

Ussuri-1 milestone

12 December, 2019 is the Ussuri-1 milestone. See project-specific notes for relevant deadlines.

Ussuri Community Goals Acknowledgement

Teams should prepare their acknowledgement of the community-wide goals for Ussuri.

Ussuri-2 milestone

13 February, 2020 is the Ussuri-2 milestone. See project-specific notes for relevant deadlines.

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.

Ussuri-3 milestone

9 April, 2020 is the Ussuri-3 milestone. See project-specific notes for relevant deadlines.

Ussuri Community Goals Completed

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

Extra-ATCs deadline

Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Those names should be added to the governance repo for consideration as ATC for the future.

Feature freeze

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

Requirements freeze

After the Ussuri-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.

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

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.

RC1 target week

The week of 20 April 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 4 May 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).

Ussuri release

The Ussuri coordinated release will happen on Wednesday, 13 May, 2020.

Project-specific events

Manila

Manila Spec Freeze

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

Manila 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 Feature Freeze

All new Manila features must be merged by the end of the week. The Ussuri releases for the OpenStack Dashboard plugin (manila-ui) and the python SDK / CLI library (python-manilaclient) will be made by the end of the week.

Oslo

Oslo Feature Freeze

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

PTL Elections

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.