Define TC-approved release in a resolution

The TC-approved release was previously defined using a tag, but was
recently redefined to include all official deliverables. Rather than
continue using the tag index page to define it, clearly define it in
a formal TC resolution, making it easier to find.

Change-Id: I15deaf54fb7c1b390e68b065eeb801dcdbb99a94
This commit is contained in:
Thierry Carrez 2020-09-16 16:45:13 +02:00
parent 0453e047ec
commit 81c90c6826
2 changed files with 18 additions and 4 deletions

View File

@ -25,10 +25,6 @@ TC Managed Tags
starter-kit_compute
starter-kit_kubernetes-in-virt
OpenStack Technical Committee Approved Release
----------------------------------------------
All deliverables created by our `Official OpenStack Projects Teams <https://governance.openstack.org/tc/reference/projects/index.html>`_
are "OpenStack Technical Committee Approved Release".
Team Description Tags
=====================

View File

@ -0,0 +1,18 @@
=======================================================
2020-09-20 'OpenStack TC approved release' definition
=======================================================
The OpenStack Foundation bylaws require that the Technical Committee
designates a subset of the OpenStack project as "OpenStack Technical
Committee Approved Release". A subset of that subset is then used by the
board to determine "Trademark Designated OpenStack Software".
Historically, the TC used a tag to define which deliverables among
OpenStack official deliverables were part of the "OpenStack Technical
Committee Approved Release". However it recently made the decision to
stop using a tag, and consider all official deliverables to be part of it.
This TC resolution therefore affirms that the "OpenStack Technical Committee
Approved Release", as far as the OpenStack Foundation bylaws are concerned,
shall consist of *all* deliverables created by official
:doc:`../reference/projects/index`.