openstack/neutron
Code Issues Proposed changes

devref: don't suggest to manually request stable branches

Browse Source 
openstack/releases now has proper automation for branch creation, based
on directory layout, so there is no longer a need to ask for a branch
explicitly.

This also kills 'release' Launchpad tag since there is no more a use
case to use it.

Change-Id: Ia98436e9e92290f838ee6360ad4399b1585e8e50
See: http://lists.openstack.org/pipermail/openstack-dev/2016-December/108923.html
This commit is contained in:
Ihar Hrachyshka 2016-12-09 11:50:17 +00:00
parent 920ddeaf58
commit 464397f7d8
2 changed files with 16 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/policies/bugs.rst
View File

@ -410,8 +410,6 @@ more will be added over time if needed.
+-------------------------------+-----------------------------------------+----------------------+
| qos_ | A bug affecting ML2/QoS | Miguel Ajo |
+-------------------------------+-----------------------------------------+----------------------+
| release_ | A request from a subproject | Darek Smigiel |
+-------------------------------+-----------------------------------------+----------------------+
| rfe_ | Feature enhancements being screened | Drivers Team |
+-------------------------------+-----------------------------------------+----------------------+
| rfe-approved_ | Approved feature enhancements | Drivers Team |
@ -709,14 +707,6 @@ QoS
* `QoS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=qos>`_
* `QoS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=qos>`_
.. _release:
Requests from Stadium Subprojects
+++++++++++++++++++++++++++++++++
* `Requests from Stadium Subprojects - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=release>`_
* `Requests from Stadium Subprojects - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=release>`_
.. _rfe:
RFE

24
doc/source/stadium/guidelines.rst
View File

@ -153,14 +153,22 @@ To release a sub-project, follow the following steps:
<https://git.openstack.org/cgit/openstack/releases/tree/README.rst>`_ a patch
to openstack/releases repository with the intended git hash. `The Neutron
release liaison <https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management>`_
should be added in Gerrit to the list of reviewers for the patch. Note: new
major tag versions should conform to `SemVer <http://semver.org/>`_
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 <https://review.openstack.org/#/c/404078/>`_.
should be added in Gerrit to the list of reviewers for the patch.
.. note::
New major tag versions should conform to `SemVer <http://semver.org/>`_
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.
.. note::
Before Ocata, when releasing the very first release in a stable series, a
sub-project owner would need to request a new stable branch creation
during Gerrit review, but not anymore. `See the following email for more
details <http://lists.openstack.org/pipermail/openstack-dev/2016-December/108923.html>`_.
* 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