From e8a3a7eb967891d6874cfdc25dcea826dbf9bfd4 Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann Date: Mon, 10 Apr 2023 17:49:09 -0500 Subject: [PATCH] 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 --- doc/source/repository.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/source/repository.rst b/doc/source/repository.rst index b95e841..ecb4bed 100644 --- a/doc/source/repository.rst +++ b/doc/source/repository.rst @@ -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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~