openstack/releases
Code Issues Proposed changes

Document how to fix release circular dependencies

Browse Source 
openstack/releases has a number of dependencies, and some of them (reno,
pbr, openstack-governance) are released using openstack/releases itself.

This may create circular dependencies issues, if one of those
dependencies becomes uninstallable: in that case we won't be able to use
openstack/releases to release a fixed version.

The proper way to solve this issue is to push a tag manually to trigger
the release of the affected repository, then retroactively push the
corresponding openstack/releases change. This will be a noop tag-wise
but make sure that the metadata is correct going forward.

This patch leaves comments in the affected files, so that we remember
how to solve this next time it happens!

Change-Id: I695e83410ba704e9978147e226e9555890a848a8
This commit is contained in:
Thierry Carrez 2021-11-25 15:20:49 +01:00
parent f98b318277
commit 04adb037c5
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