[openstack-dev] [releease][ptl] Missing and forced releases

Sean McGinnis sean.mcginnis at gmx.com
Fri Aug 3 16:52:06 UTC 2018


Today the release team reviewed the rocky deliverables and their releases done
so far this cycle. There are a few areas of concern right now.

Unreleased cycle-with-intermediary
==================================
There is a much longer list than we would like to see of
cycle-with-intermediary deliverables that have not done any releases so far in
Rocky. These deliverables should not wait until the very end of the cycle to
release so that pending changes can be made available earlier and there are no
last minute surprises.

For owners of cycle-with-intermediary deliverables, please take a look at what
you have merged that has not been released and consider doing a release ASAP.
We are not far from the final deadline for these projects, but it would still
be good to do a release ahead of that to be safe.

Deliverables that miss the final deadline will be at risk of being dropped from
the Rocky coordinated release.

Unrelease client libraries
==========================
The following client libraries have not done a release:

python-cloudkittyclient
python-designateclient
python-karborclient
python-magnumclient
python-searchlightclient*
python-senlinclient
python-tricircleclient

The deadline for client library releases was last Thursday, July 26. This
coming Monday the release team will force a release on HEAD for these clients.

* python-searchlight client is currently planned on being dropped due to
  searchlight itself not having met the minimum of two milestone releases
  during the rocky cycle.

Missing milestone 3
===================
The following projects missed tagging a milestone 3 release:

cinder
designate
freezer
mistral
searchlight

Following policy, a milestone 3 tag will be forced on HEAD for these
deliverables on Monday.

Freezer and searchlight missed previous milestone deadlines and will be dropped
from the Rocky coordinated release.

If there are any questions or concerns, please respond here or get ahold of
someone from the release management team in the #openstack-release channel.

--
Sean McGinnis (smcginnis)




More information about the OpenStack-dev mailing list