[release] Release countdown for week R-3, April 20 - 24

Sean McGinnis sean.mcginnis at gmx.com
Fri Apr 17 12:48:00 UTC 2020

Development Focus

The Release Candidate (RC) deadline is next Thursday, April 23. Work
should be focused on fixing any release-critical bugs.

General Information

All deliverables released under a cycle-with-rc model should have a first
release candidate by the end of the week, from which a stable/ussuri
branch will be cut. This branch will track the ussuri release.

Once stable/ussuri has been created, master will be ready to switch
to victoria development. While master will no longer be feature-frozen,
please prioritize any work necessary for completing ussuri plans.
Release-critical bugfixes will need to be merged in the master branch
first, then backported to the stable/ussuri branch before a new release
candidate can be proposed.


Early in the week, the release team will be proposing RC1 patches for all
cycle-with-rc projects, using the latest commit from master. If your team
is ready to go for cutting RC1, please let us know by leaving a +1 on these

If there are still a few more patches needed before RC1, you can -1 the
patch and update it later in the week with the new commit hash you would
like to use. Remember, stable/ussuri branches will be created with this,
so you will want to make sure you have what you need included to avoid
needing to backport changes from master (which will technically then be
victoria) to this stable branch for any additional RCs before the final

The release team will also be proposing releases for any deliverable
following a cycle-with-intermediary model that has not produced any ussuri
release so far.

Upcoming Deadlines & Dates

RC1 deadline: April 23 (R-3 week)
Final RC deadline: May 7 (R-1 week)
Final Ussuri release: May 13
Virtual Victoria PTG: June 1-5

More information about the openstack-discuss mailing list