Now that the final 2014.2.4 release[1] is behind us I have followed our usual end of life steps for stable/juno branches on repos under the control of the OpenStack Release Cycle Management (and future Stable Branch Maintenance) project-team. Specifically, for any repos with the release:managed[2] and release:has-stable-branches[3] governance tags, all open change reviews were abandoned for stable/juno. Then the final states of the branches were tagged as "juno-eol" and the branches subsequently deleted. The specific list of 44 Git repositories on which this action was taken (release:managed release:has-stable-branches projects with stable/juno branches, but also openstack-dev/devstack, openstack-dev/grenade, openstack/oslo-incubator and openstack/requirements at the request of the QA and Oslo project-teams) is: - openstack-dev/devstack - openstack-dev/grenade - openstack/barbican - openstack/ceilometer - openstack/cinder - openstack/designate - openstack/glance - openstack/heat - openstack/horizon - openstack/ironic - openstack/keystone - openstack/keystonemiddleware - openstack/manila - openstack/neutron - openstack/neutron-fwaas - openstack/neutron-lbaas - openstack/neutron-vpnaas - openstack/nova - openstack/oslo-incubator - openstack/oslo.concurrency - openstack/oslo.config - openstack/oslo.db - openstack/oslo.i18n - openstack/oslo.messaging - openstack/oslo.middleware - openstack/oslo.rootwrap - openstack/oslo.utils - openstack/oslo.vmware - openstack/oslotest - openstack/pycadf - openstack/python-ceilometerclient - openstack/python-glanceclient - openstack/python-keystoneclient - openstack/python-neutronclient - openstack/python-swiftclient - openstack/requirements - openstack/sahara - openstack/sahara-extra - openstack/sahara-image-elements - openstack/swift - openstack/taskflow - openstack/tooz - openstack/trove - openstack/zaqar An additional 64 repos[4] still have stable/juno branches. If the maintainers of any of those wish to have them deleted: please abandon any remaining open changes for the branch in Gerrit and push a tag if desired, then get in touch with the Infrastructure team either in the #openstack-infra IRC channel on Freenode or through the openstack-infra@lists.openstack.org mailing list to request a branch deletion. [1] http://lists.openstack.org/pipermail/openstack-announce/2015-November/000794... [2] http://governance.openstack.org/reference/tags/release_managed.html [3] http://governance.openstack.org/reference/tags/release_has-stable-branches.h... [4] http://paste.openstack.org/show/481087 -- Jeremy Stanley