openstack/glance-specs
Code Issues Proposed changes
481b222894
glance-specs/priorities
History
ghanshyam mann 666e70eef5 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
2022-09-01 00:21:44 +05:30
..
2023.1-priorities.rst Using release number as primary identifier 2022-09-01 00:21:44 +05:30
mitaka-priorities.rst Add Glance priorities for Mitaka 2015-10-30 01:29:29 +00:00
newton-priorities.rst Add newton priorities 2016-11-22 15:59:46 -05:00
ocata-priorities.rst Update http to https 2022-04-29 21:43:25 +00:00
pike-priorities.rst Update http to https 2022-04-29 21:43:25 +00:00
queens-priorities.rst Update http to https 2022-04-29 21:43:25 +00:00
rocky-priorities.rst Add release dates to Rocky priorities page 2018-03-26 19:10:19 -04:00
stein-priorities.rst Create specs directory for Stein 2018-08-27 21:11:02 -04:00
train-priorities.rst Add priorities to Train page 2019-09-05 16:46:55 -04:00
ussuri-priorities.rst Ussuri project priorities 2019-12-13 05:24:09 +00:00
victoria-priorities.rst Create specs directory for Victoria cycle 2020-04-23 17:28:08 +00:00
wallaby-priorities.rst Create specs directory for Wallaby cycle 2020-09-14 05:30:56 +00:00
xena-priorities.rst Add xena directory for specs 2021-03-15 14:29:42 +00:00
yoga-priorities.rst Add Yoga directory for specs 2021-09-02 18:33:11 +00:00
zed-priorities.rst Add Zed direcotry for specs 2022-02-15 06:08:46 +00:00