openstack
/
releases
Code Issues Proposed changes

Merge "Document how to fix release circular dependencies"

This commit is contained in:
Zuul 2022-05-13 14:07:42 +00:00 committed by Gerrit Code Review
parent c3b3c3ca1d 04adb037c5
commit d0f8eda9be
3 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
deliverables/_independent/openstack-governance.yaml
View File

@ -1,4 +1,11 @@
---
# Governance is a dependency of openstack/releases itself. This may create
# an issue should governance become uninstallable, as we won't be able to
# use openstack/releases to release a fixed version.
# Should this situation ever occur again, the proper way to fix it is to
# push a tag to governance manually, then retroactively submit the
# corresponding change to openstack/releases. The change will update the
# metadata while otherwise being a noop.
storyboard: 923
team: Technical Committee
type: library

7
deliverables/_independent/pbr.yaml
View File

@ -1,4 +1,11 @@
---
# PBR is a dependency of openstack/releases itself. This may create an
# issue should PBR become uninstallable, as we won't be able to use
# openstack/releases to release a fixed version.
# Should this situation ever occur again, the proper way to fix it is to
# push a tag to PBR manually, then retroactively submit the corresponding
# change to openstack/releases. The change will update the metadata while
# otherwise being a noop.
launchpad: pbr
team: oslo
type: library

7
deliverables/_independent/reno.yaml
View File

@ -1,4 +1,11 @@
---
# Reno is a dependency of openstack/releases itself. This may create an
# issue should PBR become uninstallable, as we won't be able to use
# openstack/releases to release a fixed version.
# Should this situation ever occur again, the proper way to fix it is to
# push a tag to Reno manually, then retroactively submit the corresponding
# change to openstack/releases. The change will update the metadata while
# otherwise being a noop.
storyboard: 933
team: Release Management
type: other