diff options
| author | Zuul <zuul@review.opendev.org> | 2023-08-02 13:16:15 +0000 |
|---|---|---|
| committer | Gerrit Code Review <review@openstack.org> | 2023-08-02 13:16:15 +0000 |
| commit | bd68acb60fe850534541347d7d44091927c5f416 (patch) | |
| tree | 1165ebe94350084bfb1be5f891cadc87650486cd | |
| parent | 1841cc852da0adaada3bf29398c9e3f6a48ccbec (diff) | |
| parent | beab44f3a2f29fa8ec7fe8a13ebe7331fba4dd7e (diff) | |
| download | kolla-bd68acb60fe850534541347d7d44091927c5f416.tar.gz kolla-bd68acb60fe850534541347d7d44091927c5f416.zip | |
Merge "Update stable branch management doc"
| -rw-r--r-- | doc/source/contributor/release-management.rst | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/source/contributor/release-management.rst b/doc/source/contributor/release-management.rst index 8006e1492..e56297eed 100644 --- a/doc/source/contributor/release-management.rst +++ b/doc/source/contributor/release-management.rst @@ -464,14 +464,11 @@ a recurring topic for that in the first Kolla meeting each month. * you can use the tooling from the requirements team to prepare the patches:: git checkout -b kolla-stable-monthly - for project in kayobe kolla kolla-ansible; do - for rel in xena yoga zed; do + for project in ansible-collection-kolla kayobe kolla kolla-ansible; do + for rel in yoga zed antelope; do tox -e venv -- new-release $rel $project feature done done - for rel in yoga zed; do - tox -e venv -- new-release $rel ansible-collection-kolla feature - done git commit -am "Tag monthly kolla stable releases" git review -f |
