openstack
/
project-team-guide
Code Issues Proposed changes

Cover the branchless repo in deprecation process 

When we deprecate the branchless repo (for example, tempest
or any other tests repo), sometime they need to support the
other deliverables stable branches. In that case we cannot
remove those branchless repo master branch content. We can just
update the README.rst file to reflect the deprecation and postponed
the master branch content removal until all deps are either retired
or EOL.

One such case is TripleO test repo
- https://review.opendev.org/c/openstack/governance/+/877132/2/reference/projects.yaml#2846

Change-Id: Ie8cbd77bb4fa2914f42e2c5cf6cd6fdc2d116bd3
This commit is contained in:
Ghanshyam Mann 2023-04-10 17:49:09 -05:00
parent 824304d561
commit e8a3a7eb96
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/repository.rst
View File

@ -209,6 +209,11 @@ NOTE: use Depends-On on ``governance`` patch submitted in Step 1.
Step 3: Retire master branch
----------------------------
If the repository is branchless (for example, Tempest and its plugins) and
its master branch content needs to support the other deliverables stable branch
until they are retired or reach EOL, then you can skip this Step 3 and update
only README.rst file to reflect the deprecation notes.
Step 3a: Use only noop jobs
~~~~~~~~~~~~~~~~~~~~~~~~~~~