[release] Release countdown for week R-4, April 13 - 17
sean.mcginnis at gmx.com
Fri Apr 10 13:58:59 UTC 2020
We just passed feature freeze! Until release branches are cut, you
should stop accepting featureful changes to deliverables following the
cycle-with-rc release model, or to libraries. Exceptions should be
discussed on separate threads on the mailing-list, and feature freeze
exceptions approved by the team's PTL.
Focus should be on finding and fixing release-critical bugs, so that
release candidates and final versions of the ussuri deliverables can be
proposed, well ahead of the final ussuri release date.
We are still finishing up processing a few release requests, but the
ussuri release requirements are now frozen. If new library releases are
needed to fix release-critical bugs in ussuri, you must request a
Requirements Freeze Exception (RFE) from the requirements team before we
can do a new release to avoid having something released in ussuri that
is not actually usable. This is done by posting to the openstack-discuss
mailing list with a subject line similar to:
[$PROJECT][requirements] RFE requested for $PROJECT_LIB
Include justification/reasoning for why a RFE is needed for this lib.
If/when the requirements team OKs the post-freeze update, we can then
process a new release.
A soft String freeze is now in effect, in order to let the I18N team do the
translation work in good conditions. In Horizon and the various dashboard
plugins, you should stop accepting changes that modify user-visible
strings. Exceptions should be discussed on the mailing-list. By
April 23 this will become a hard string freeze, with no changes
in user-visible strings allowed.
stable/ussuri branches should be created soon for all not-already-branched
libraries. You should expect 3-4 changes to be proposed for each: a
.gitreview update, a reno update (skipped for projects not using reno),
a tox.ini constraints URL update, and a patch updating any cycle-specific
job templates to the victoria version. Please review those in priority
so that the branch can be functional ASAP. Note that the victoria job
templates may not be quite ready yet, so the patch may initially fail. A
simple recheck once they are in place should allow the patch to pass.
The Prelude section of reno release notes is rendered as the top level
overview for the release. Any important overall messaging for ussuri
changes should be added there to make sure the consumers of your release
notes see them.
Finally, if you haven't proposed ussuri cycle-highlights yet, you are
already late to the party. Please see
Upcoming Deadlines & Dates
RC1 deadline: April 23 (R-3 week)
Final RC deadline: May 7 (R-1 week)
Final Ussuri release: May 13
More information about the openstack-discuss