From c0983a19a4bb88cd50b69d46e58d503a3003cbda Mon Sep 17 00:00:00 2001 From: YAMAMOTO Takashi Date: Mon, 5 Dec 2016 15:03:45 +0900 Subject: [PATCH] stadium guidelines: Document stable branch creation Change-Id: If014b9bff7f4c281215f09ebe1580bbc376a56dd --- doc/source/stadium/guidelines.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/source/stadium/guidelines.rst b/doc/source/stadium/guidelines.rst index 452c94b06a3..3060b91b583 100644 --- a/doc/source/stadium/guidelines.rst +++ b/doc/source/stadium/guidelines.rst @@ -138,7 +138,6 @@ All subproject releases are managed by `global OpenStack Release Managers team `_ handles only the following operations: -* Create stable branches * Make stable branches end of life To release a sub-project, follow the following steps: @@ -159,6 +158,9 @@ To release a sub-project, follow the following steps: 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. +* If your project is release:independent and it's the first release for + a branch, you should create the stable branch similarly to + `the patch for networking-midonet's stable/newton branch `_. * 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