[release] (Belated) Release countdown for week R-12, July 22-26
The Train-2 milestone is July 25! Train-related specs should now be
finalized so that teams can move to implementation ASAP. Some teams observe
specific deadlines on the second milestone (mostly spec freezes): please
refer to https://releases.openstack.org/train/schedule.html for details.
Libraries need to be released at least once per milestone period. This week,
the release team will propose releases for any library that has not been
otherwise released since milestone 1. See list at:
http://paste.openstack.org/show/754817/. PTL's and release liaisons, please
watch for these and give a +1 to acknowledge them. If there is some reason
to hold off on a release, let us know that as well. A +1 would be
appreciated, but if we do not hear anything at all by the end of the week,
we will assume things are OK to proceed.
Remember that non-library deliverables that follow the
cycle-with-intermediary release model should have an intermediary release
before milestone-2. Those who haven't will be proposed to switch to the
cycle-with-rc model, which is more suited to deliverables that are released
only once per cycle.
This week is also the deadline to freeze the contents of the final release.
All new 'Train' deliverables need to have a deliverable file (
and need to have done a release by milestone-2. The following new
deliverables have not had a release yet (or not been already discussed in
the etherpad), and will not be included in Train unless a release is
requested for them in the coming week: python-adjutantclient,
cyborg-tempest-plugin, neutron-interconnection, openstack-helm,
openstack-helm-addons, openstack-help-docs, openstack-helm-images,
openstack-helm-infra, and compute-hyperv. The full list of currently
deliverable-less deliverables can be found here.
Upcoming Deadlines & Dates
Train-2 Milestone: July 25 (R-12 week)
-Kendall Nelson(diablo_rojo) + the Release Management Team
-------------- next part --------------
An HTML attachment was scrubbed...