Release liaisons, As described in [1], we are changing our stable release policy for Liberty to encourage projects to tag new releases when they have patches ready to be released. There is a script in the openstack-infra/release-tools repository to make it easier to keep track of what has not yet been released.
The list_unreleased_changes.sh script takes 2 arguments, the branch name and the repository name(s). It clones a temporary copy of the repositories and looks for changes since the last tag on the given branch. For example: $ ./list_unreleased_changes.sh stable/liberty openstack/glance [ Cloning openstack/glance ] INFO:zuul.CloneMapper:Workspace path set to: /mnt/projects/release-tools/release-tools/list-unreleased-kFv INFO:zuul.CloneMapper:Mapping projects to workspace... INFO:zuul.CloneMapper: openstack/glance -> /mnt/projects/release-tools/release-tools/list-unreleased-kFv/openstack/glance INFO:zuul.CloneMapper:Expansion completed. INFO:zuul.Cloner:Preparing 1 repositories INFO:zuul.Cloner:Creating repo openstack/glance from upstream git://git.openstack.org/openstack/glance INFO:zuul.Cloner:upstream repo has branch stable/liberty INFO:zuul.Cloner:Falling back to branch stable/liberty INFO:zuul.Cloner:Prepared openstack/glance repo with branch stable/liberty INFO:zuul.Cloner:Prepared all repositories Creating a git remote called "gerrit" that maps to: ssh://doug-hellm...@review.openstack.org:29418/openstack/glance.git [ Unreleased changes in openstack/glance ] Changes in glance 11.0.0..a50026b --------------------------------- 53d48d8 2015-11-03 18:00:26 +0000 add first reno-based release note 4a31949 2015-11-03 18:00:26 +0000 set default branch for git review aae81e2 2015-10-23 15:52:53 +0000 Updated from global requirements b977544 2015-10-22 07:03:47 +0000 Pass CONF to logging setup 25ead6a 2015-10-18 10:12:26 +0000 Fixed registry invalid token exception handling 5434297 2015-10-17 10:40:42 +0000 Updated from global requirements 8902d12 2015-10-16 10:34:46 +0000 Decrease test failure if second changes during run 7158d78 2015-10-15 15:43:15 +0200 Switch to post-versioning [ Cleaning up ] When you decide that it is time to prepare a new release, submit a patch to the openstack/releases repository with the SHA, version, and other info. See the README there for more details. Doug [1] http://lists.openstack.org/pipermail/openstack-dev/2015-November/078281.html __________________________________________________________________________ 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