openstack
/
governance
Code Issues Proposed changes

Move application to current projects up in tag page 

Feedback from operators in a user committee session pointed out which
projects a tag is applied to is one of the most useful things on each
tag's page.  So move the 'application to current projects' section up in
the page so it is easier to find.

Change-Id: Ib7b0aa250f950398e0abd20d35a1ea252b057d4c
This commit is contained in:
Joe Gordon 2015-05-20 11:34:29 -07:00
parent a7737b2285
commit 57e0cefc36
7 changed files with 60 additions and 59 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
reference/tag-template.rst
View File

@ -24,6 +24,18 @@ proposed-tag-name (should match the tags/proposed-tag-name.rst filename)
Introduction paragraph -- a short summary of what this tag will mean.
Application to current projects
===============================
As part of the application you need to go through the exercise of applying
the proposed tag to at least some subset of the current project list. This
will serve as an example of how the tag should be applied in the real world.
You may also submit (as a subsequent change) the corresponding governance
change to immediately apply the proposed tag to projects.
.. tagged-projects:: <tag name>
Rationale
=========
@ -81,15 +93,3 @@ example-attribute
Description of the example-attribute tag attribute, and of the values it may
take.
Application to current projects
===============================
As part of the application you need to go through the exercise of applying
the proposed tag to at least some subset of the current project list. This
will serve as an example of how the tag should be applied in the real world.
You may also submit (as a subsequent change) the corresponding governance
change to immediately apply the proposed tag to projects.
.. tagged-projects:: <tag name>

20
reference/tags/integrated-release.rst
View File

@ -14,6 +14,16 @@ The integrated-release tag describes projects that were "integrated"
in the previous project structure.
Application to current projects
===============================
The following code repositories would get the proposed tag. Those match the
contents of the Kilo release as decided at the end of the Juno cycle, and
take into account the recent Neutron advanced services code split:
.. tagged-projects:: integrated-release
Rationale
=========
@ -60,13 +70,3 @@ since
This attribute describes the development cycle where the project was first
fully integrated (and therefore the first release name where the project was
included). Example values: folsom, kilo
Application to current projects
===============================
The following code repositories would get the proposed tag. Those match the
contents of the Kilo release as decided at the end of the Juno cycle, and
take into account the recent Neutron advanced services code split:
.. tagged-projects:: integrated-release

12
reference/tags/release_at-6mo-cycle-end.rst
View File

@ -21,6 +21,12 @@ Note that it doesn't prevent those projects from also producing intermediary
releases in the middle of a development cycle.
Application to current projects
===============================
.. tagged-projects:: release:at-6mo-cycle-end
Rationale
=========
@ -60,9 +66,3 @@ Attributes
==========
Tags in the "release" category do not use attributes.
Application to current projects
===============================
.. tagged-projects:: release:at-6mo-cycle-end

12
reference/tags/release_has-stable-branches.rst
View File

@ -21,6 +21,12 @@ libraries. They are cut from the last release in the cycle for a given code
repository.
Application to current projects
===============================
.. tagged-projects:: release:has-stable-branches
Rationale
=========
@ -59,9 +65,3 @@ Attributes
==========
Tags in the "release" category do not use attributes.
Application to current projects
===============================
.. tagged-projects:: release:has-stable-branches

12
reference/tags/release_independent.rst
View File

@ -17,6 +17,12 @@ any other project. Releasing in this fashion doesn't prevent projects from
also releasing a "final" release at the end of a development cycle.
Application to current projects
===============================
.. tagged-projects:: release:independent
Rationale
=========
@ -49,9 +55,3 @@ Attributes
==========
Tags in the "release" category do not use attributes.
Application to current projects
===============================
.. tagged-projects:: release:independent

12
reference/tags/release_managed.rst
View File

@ -15,6 +15,12 @@ model for a given code repository. Projects tagged with "release:managed" tag
are those who are directly managed by the Release Management team.
Application to current projects
===============================
.. tagged-projects:: release:managed
Rationale
=========
@ -60,9 +66,3 @@ Attributes
==========
Tags in the "release" category do not use attributes.
Application to current projects
===============================
.. tagged-projects:: release:managed

27
reference/tags/team_diverse-affiliation.rst
View File

@ -16,6 +16,20 @@ exists in the 'team' category, which as the name implies, covers information
about the team itself. Another example of a tag that could exist in this
category is one that conveys the size of the team that is actively contributing.
Application to current projects
===============================
It's worth pointing out that the criteria used for this tag is applied across
all git repositories managed by a team.
.. tagged-projects:: team:diverse-affiliation
Script used to apply this tag:
http://git.openstack.org/cgit/openstack/governance/tree/tools/validate_tags.py
Rationale
=========
@ -78,16 +92,3 @@ Attributes
==========
This tag has no attributes.
Application to current projects
===============================
It's worth pointing out that the criteria used for this tag is applied across
all git repositories managed by a team.
.. tagged-projects:: team:diverse-affiliation
Script used to apply this tag:
http://git.openstack.org/cgit/openstack/governance/tree/tools/validate_tags.py