releases/openstack_releases/series_status_schema.yaml
Előd Illés 2b8ee3aaec Fix upper-constraints redirect for new release naming
The new release identification / naming schema [1] (like:
2023.1 Antelope) broke the redirection rules for branch specific upper
constraint files as the stable branch names are from now on based on
the new release identification (like: stable/2023.1).

This patch fixes the redirections by introducing the release ID field
to series status, to translate a release name to 'stable/<release-id>'
where this ID exists.

[1] https://governance.openstack.org/tc/reference/release-naming.html

Change-Id: Iab885d4e36f64903b323e16c74d8315c759584de
2023-01-14 10:29:27 +01:00

54 lines
1.1 KiB
YAML

---
$schema: "http://json-schema.org/schema#"
$id: "https://opendev.org/openstack/releases/src/branch/master/README.rst"
# Do not allow any properties not defined here. This lets us catch
# typos.
additionalProperties: false
type: "array"
items:
type: "object"
additionalProperties: false
required:
- name
- status
properties:
name:
type: "string"
release-id:
type: "number"
status:
type: "string"
enum:
- future
- development
- maintained
- extended maintenance
- unmaintained
- end of life
slurp:
type: "string"
initial-release:
type: "date"
eol-date:
type: "date"
next-phase:
type: "object"
additionalProperties: false
properties:
required:
- status
- date
status:
type: "string"
enum:
- future
- development
- maintained
- extended maintenance
- unmaintained
- end of life
date:
type: "date"