openstack
/
project-team-guide
Code Issues Proposed changes

a few clarifying updates 

Change-Id: Ic4bbd2b02eef0165e9a4748ce9ac61a3409468c5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2017-06-22 13:01:35 -04:00
parent f4a1671703
commit ae1090d242
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/source/open-community.rst
View File

@ -125,7 +125,8 @@ of elected technical positions in OpenStack:
The *project team* guide naturally focuses on PTLs. More information about the
TC can be found on the `Technical Committee website`_. You can reach out to
TC members using the openstack-dev mailing-list (with the [tc] prefix), or
TC members using the openstack-dev mailing-list (including the ``[tc]`` "tag"
in your subject line will make it more likely for them to see the message), or
on the #openstack-tc IRC channel (especially around `TC office hours`_).
Each project team in OpenStack needs a PTL. The PTL is an elected leader who

2
doc/source/release-management.rst
View File

@ -109,7 +109,7 @@ the team decided to more directly handle release management.
Projects following this model do not use intermediary development milestones.
They may request publication of versions at any point in time during the
development cycle. They do not use Feature Freeze, they do not go through a
release candidate cycle. Every tag is a release supposed to be consumable by
release candidate cycle. Every tag is a release that should be be consumable by
users. They use a post-version semver-based numbering scheme, where every tag
is a X.Y.Z version.