[openstack-dev] [release] Release countdown for week R-4, January 27 - February 2
sean.mcginnis at gmx.com
Thu Jan 25 14:00:11 UTC 2018
Happy deadline week everyone. Here's what's coming up for next week.
The R-4 week is our one deadline free week between the lib freezes and Queens-3
milestone and RC.
Work should be focused on fixing any requirements update issues, critical bugs,
and wrapping up feature work to prepare for the Release Candidate deadline (for
deliverables following the with-milestones model) or final Queens releases (for
deliverables following the with-intermediary model) next Thursday, 8th of
For deliverables following the cycle-with-milestones model, we are now past
Feature Freeze. The focus should be on determining and fixing release-critical
bugs. At this stage only bugfixes should be approved for merging in the master
branches: feature work should only be considered if explicitly granted a
Feature Freeze exception by the team PTL (after a public discussion on the
StringFreeze is now in effect, in order to let the I18N team do the translation
work in good conditions. The StringFreeze is currently soft (allowing
exceptions as long as they are discussed on the mailing-list
and deemed worth the effort). It will become a hard StringFreeze on 8th of
February along with the RC.
The requirements repository is also frozen, until all cycle-with-milestones
deliverables have produced a RC1 and have their stable/queens branches.
Note that deliverables that are not tagged for release by the appropriate
deadline will be reviewed to see if they are still active enough to stay on the
official project list.
stable/queens branches should be created soon for all non-already-branched
libraries. You should expect 2-3 changes to be proposed for each: a .gitreview
update, a reno update (skipped for projects not using reno), and a tox.ini
constraints URL update. Please review those in priority so that the branch can
be functional ASAP.
For cycle-with-intermediary deliverables, release liaisons should consider
releasing their latest version, and creating stable/queens branches from it
For cycle-with-milestones deliverables, release liaisons should wait until R-3
week to create RC1 (to avoid having an RC2 created quickly after). Review
release notes for any missing information, and start
preparing "prelude" release notes as summaries of the content of the release so
that those are merged before the first release candidate.
Along with the prelude work, it is also a good time to start planning what
highlights you want for your project team in the cycle highlights:
For release-independent deliverables, release liaisons should check that their
deliverable file includes all the existing releases, so that they can be
properly accounted for in the releases.openstack.org website.
If your team has not done so, remember to file Queens goal completion
information, as explained in:
Upcoming Deadlines & Dates
Rocky PTL nominations: January 29 - February 1
Rocky PTL election: February 7 - 14
OpenStack Summit Vancouver CFP deadline: February 8
Rocky PTG in Dublin: Week of February 26, 2018
Sean McGinnis (smcginnis)
More information about the OpenStack-dev