openstack/governance
Code Issues Proposed changes

Clarify impact on releases for SIGs

Browse Source 
SIGs are not using release tooling, but they can/should
create tags and manage their code as usual.

The explanation about release implication for SIGs was
not very explicit, so this should clarify it.

Change-Id: I6e0bb44743a47cc2df354f0ed9ac6915272f114a
This commit is contained in:
Jean-Philippe Evrard 2020-09-18 15:41:32 +02:00 committed by Ghanshyam
parent 09e37871b3
commit 2868fbceb2
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
reference/comparison-of-official-group-structures.rst
View File

@ -66,7 +66,10 @@ limited accountability is required, and SIGs do not have any required named
liaisons. liaisons.
SIGs can own git repositories and produce software, but that software will be SIGs can own git repositories and produce software, but that software will be
considered add-on software to the main "OpenStack" software releases. considered add-on software to the main "OpenStack" software releases. Therefore
SIGs deliverables are not part of the coordinated release, and will not leverage
the openstack/releases repository. If a SIG does release any tooling or software
they are responsible for any release management/tagging needed.
You can check for `process to create a SIG`_ for creating a new SIG. You can check for `process to create a SIG`_ for creating a new SIG.