We have branched the openstack/requirements repository as the first step to unfreezing requirements changes in master. Creating the branch triggered the requirements update bot to propose changes to repositories with stable/mitaka branches that were out of sync relative to the point where we branched. Most of those repositories are for libraries, but there are one or two server projects in the list as well.
These updates are mostly changes we made to the requirements list after it was frozen in order to address issues such as bad versions of libraries, needed patch updates, etc. Some may also reflect requirements updates that were not merged into the repositories before their stable branches were created. We want to have the stable branch requirements updates cleaned up to avoid the limbo state we were in with liberty for so long, where no one was confident of merging requirements changes in the stable branch. We need project teams to review and land the patches, then prepare release requests for the affected projects as soon as possible. Please look through the list of patches [1] and give them a careful but speedy review, then submit a change to openstack/releases for the new release using a minimum-version level update (increment the Y from X.Y.Z and reset Z to 0) reflecting the change in requirements. Thanks, Doug [1] https://review.openstack.org/#/q/is:open+branch:stable/mitaka+topic:openstack/requirements __________________________________________________________________________ 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
