As the client deadline and milestone 3 day winds down here, I wanted to do a quick check on where things stand before calling it a day.
This is according to script output, so I haven't actually looked into any details so far. But according to the script, the follow cycle-with-intermediary deliverables have not had a release done for rocky yet: aodh bifrost ceilometer cloudkitty-dashboard cloudkitty ec2-api ironic-python-agent karbor-dashboard karbor kuryr-kubernetes kuryr-libnetwork magnum-ui magnum masakari-dashboard monasca-kibana-plugin monasca-log-api monasca-notification networking-hyperv panko python-cloudkittyclient python-designateclient python-karborclient python-magnumclient python-pankoclient python-searchlightclient python-senlinclient python-tricircleclient sahara-tests senlin-dashboard tacker-horizon tacker zun-ui zun Just a reminder that we will need to force a release on these in order to get a final point to branch stable/rocky. Taking a look at ones that have done a release but have had more unreleased commits since then, I'm also seeing several python-*client deliverables that may be missing final releases. Thanks, Sean On Thu, Jul 26, 2018 at 07:22:01AM -0500, Sean McGinnis wrote: > > General Information > ------------------- > > For deliverables following the cycle-with-milestones model, we are now (after > the day I send this) 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 mailing-list). > > 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 9th of August along with > the > RC. > > The requirements repository is also frozen, until all cycle-with-milestones > deliverables have produced a RC1 and have their stable/rocky branches. If > release critical library or client library releases are needed for Rocky past > the freeze dates, you must request a Feature Freeze Exception (FFE) from the > requirements team before we can do a new release to avoid having something > released in Rocky that is not actually usable. This is done by posting to the > openstack-dev mailing list with a subject line similar to: > > [$PROJECT][requirements] FFE requested for $PROJECT_LIB > > Include justification/reasoning for why a FFE is needed for this lib. If/when > the requirements team OKs the post-freeze update, we can then process a new > release. Including a link to the FFE in the release request is not required, > but would be helpful in making sure we are clear to do a new release. > > 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. > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev