Using release number as primary identifier
In Zed cycle, TC passed a resolution[1] and updated the release Identification document[2] to use the release number as primary identifier in the development cycle. Release name will be used in marketting and release team tooling (until they are migrated to work with release number) only. Let's use release number consistently across OpenStack projects. [1] https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html [2] https://governance.openstack.org/tc/reference/release-naming.html Change-Id: I513c4ebca38984b80d8e5613c3190d88fcb44aca
This commit is contained in:
parent
f5a9573aff
commit
666e70eef5
|
@ -43,7 +43,7 @@ of those discussions:
|
|||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
priorities/antelope-priorities
|
||||
priorities/2023.1-priorities
|
||||
previous-priorities
|
||||
|
||||
Specifications
|
||||
|
@ -56,7 +56,7 @@ Current
|
|||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
specs/antelope/*
|
||||
specs/2023.1/*
|
||||
specs/untargeted/*
|
||||
|
||||
.. Future
|
||||
|
|
|
@ -0,0 +1,10 @@
|
|||
.. _2023.1-priorities:
|
||||
|
||||
=========================
|
||||
2023.1 Project Priorities
|
||||
=========================
|
||||
|
||||
TODO(pdeore): fill this in after the PTG
|
||||
|
||||
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
.. _antelope-priorities:
|
||||
|
||||
===========================
|
||||
Antelope Project Priorities
|
||||
===========================
|
||||
|
||||
TODO(pdeore): fill this in after the PTG
|
||||
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
================================
|
||||
Antelope Approved Specifications
|
||||
================================
|
||||
==============================
|
||||
2023.1 Approved Specifications
|
||||
==============================
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
|
@ -0,0 +1,8 @@
|
|||
=================================
|
||||
2023.1 Implemented Specifications
|
||||
=================================
|
||||
|
||||
TODO: fill this in until a new implemented space is added.
|
||||
|
||||
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
=======================
|
||||
Antelope Specifications
|
||||
=======================
|
||||
=====================
|
||||
2023.1 Specifications
|
||||
=====================
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
Antelope implemented specs:
|
||||
2023.1 implemented specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
|
@ -14,7 +14,7 @@ Antelope implemented specs:
|
|||
|
||||
implemented/*
|
||||
|
||||
Antelope approved (but not implemented) specs:
|
||||
2023.1 approved (but not implemented) specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
|
@ -1,8 +0,0 @@
|
|||
===================================
|
||||
Antelope Implemented Specifications
|
||||
===================================
|
||||
|
||||
TODO: fill this in until a new implemented space is added.
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue