From 053448daddf793fa0d7b13d16595258fcec67f2f Mon Sep 17 00:00:00 2001 From: Ihar Hrachyshka Date: Fri, 9 Sep 2016 00:54:16 +0000 Subject: [PATCH] stadium: remove neutron-release from release job for stadium projects Now that release folks automated release process for independent projects, we should be safe to offload the whole release management process to openstack/releases machinery. Actually, leaving it up to neutron-release team is error prone (f.e. we made mistakes before with missing information in pushed git tags that held off email announcements). The idea of the change comes from Doug Hellmann. Quoting: (in reference to no announcement email for networking-sfc 2.0.0) > the email was skipped because you tagged the release by hand and the > script didn't have the metadata it needed [...] > this is why I want you to let us tag the releases. Change-Id: Idc7f85fa860b3699d457ba00e800208acecb15de --- doc/source/stadium/guidelines.rst | 24 ++++++++---------------- 1 file changed, 8 insertions(+), 16 deletions(-) diff --git a/doc/source/stadium/guidelines.rst b/doc/source/stadium/guidelines.rst index 42f13cde97e..452c94b06a3 100644 --- a/doc/source/stadium/guidelines.rst +++ b/doc/source/stadium/guidelines.rst @@ -132,16 +132,15 @@ consumers of your code easier. Sub-Project Release Process ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Only members of the `neutron-release -`_ gerrit group can do -the following release related tasks: +All subproject releases are managed by `global OpenStack Release Managers team +`_. The +`neutron-release team +`_ handles only the +following operations: -* Make releases * Create stable branches * Make stable branches end of life -Make sure you talk to a member of neutron-release to perform these tasks. - To release a sub-project, follow the following steps: * For projects which have not moved to post-versioning, we need to push an @@ -155,19 +154,12 @@ To release a sub-project, follow the following steps: `_ a patch to openstack/releases repository with the intended git hash. `The Neutron release liaison `_ - should be added in Gerrit to the list of reviewers for the patch. -* If the subproject is not `managed - `_ by - OpenStack Release Team, a member of `neutron-release - `_ `tags the release - `_ and - creates the needed stable branches, if needed. Note: tagging will release - the code to PyPI. Note: new major tag versions should conform to SemVer + should be added in Gerrit to the list of reviewers for the patch. Note: new + major tag versions should conform to `SemVer `_ requirements, meaning no year numbers should be used as a major version. The switch to SemVer is advised at earliest convenience for all new major releases. -* The Neutron release liaison votes with +1 for the openstack/releases patch - that gives indication to release team the patch is ready to merge. +* The Neutron release liaison votes with +1 for the openstack/releases patch. * The releases will now be on PyPI. A sub-project owner should verify this by going to an URL similar to `this `_.