Remove OpenStack specific steps from project retirement/rename
For Retirement: Two of the 5 steps are OpenStack specific, remove them. For rename: Some instructions are OpenStack specific, remove them. Change https://review.opendev.org/712534 adds these steps to the project-team-guide. Change-Id: I8c1aca854512ebcee54fc5c203ed3a0336ab1a05
This commit is contained in:
Andreas Jaeger
parent
e405053a4e
commit
b761af7fd3
|
|
@ -1486,28 +1486,8 @@ branches like ``stable/mitaka``. It will not run on the old
|
|||
Project Renames
|
||||
===============
|
||||
|
||||
.. note::
|
||||
|
||||
If you rename a project to move out from "openstack" namespace to
|
||||
any other namespace, follow `this OpenStack TC resolution
|
||||
<https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html>`_
|
||||
instead.
|
||||
|
||||
The first step of doing a rename is understanding the required
|
||||
governance changes needed by the rename. You can use the following
|
||||
criteria:
|
||||
|
||||
For a project being added to existing official OpenStack project:
|
||||
Create an ``openstack/governance`` change and add a "Depends-On:
|
||||
project-change-url" of the change you make in the following steps to
|
||||
the commit message, and add a comment in the
|
||||
``openstack/project-config`` change that references the
|
||||
governance change. You will also make sure the PTL has expressed
|
||||
approval for the addition in some way.
|
||||
|
||||
When preparing to rename a project, begin by making changes to the
|
||||
files in the ``openstack/project-config`` repository related
|
||||
to your project.
|
||||
When preparing to rename a project, make changes to the files in the
|
||||
``openstack/project-config`` repository related to your project.
|
||||
|
||||
When uploading your change, make sure the topic is "project-rename"
|
||||
which can be done by submitting the review with the following
|
||||
|
|
@ -1534,9 +1514,6 @@ Post rename, a member of the Infrastructure team will submit a patch to update
|
|||
the :file:`.gitreview` file in the renamed project to point to the new project
|
||||
name.
|
||||
|
||||
Other projects you may need to update post-rename:
|
||||
|
||||
* projects.txt in ``openstack/requirements``
|
||||
|
||||
Review List for New Projects
|
||||
============================
|
||||
|
|
|
|||
|
|
@ -338,9 +338,9 @@ following steps will help you wind down a project gracefully.
|
|||
.. note::
|
||||
|
||||
The following sections are really separate steps. If your project
|
||||
has jobs set up and is an official project, you need to submit
|
||||
*four* different changes as explained below. We recommend to link
|
||||
these changes with "Depends-On:" and "Needed-By:" headers.
|
||||
has jobs set up, you need to submit several different changes as
|
||||
explained below. We recommend to link these changes with
|
||||
"Depends-On:" and "Needed-By:" headers.
|
||||
|
||||
Prerequirement: Announce Retirement
|
||||
-----------------------------------
|
||||
|
|
@ -349,14 +349,7 @@ Use mailing lists or other channels to announce to users and
|
|||
contributors that the project is being retired. Be sure to include a
|
||||
date upon which maintenance will end, if that date is in the future.
|
||||
|
||||
Step 1: Stop requirements syncing (if set up)
|
||||
---------------------------------------------
|
||||
|
||||
Submit a review to the ``openstack/requirements`` project removing the
|
||||
project from ``projects.txt``. This needs to happen for stable
|
||||
branches as well.
|
||||
|
||||
Step 2: End Project Gating
|
||||
Step 1: End Project Gating
|
||||
--------------------------
|
||||
|
||||
Check out a copy of the ``openstack/project-config`` repository
|
||||
|
|
@ -377,7 +370,7 @@ Submit that change and make sure to mention in the commit message that
|
|||
you are ending project gating for the purposes of retiring the
|
||||
project. Wait for that change to merge and then proceed.
|
||||
|
||||
Step 3: Remove Project Content
|
||||
Step 2: Remove Project Content
|
||||
------------------------------
|
||||
|
||||
Once Zuul is no longer running tests on your project, prepare a change
|
||||
|
|
@ -421,7 +414,7 @@ deploy unmaintained software. Potential contributors who may not have
|
|||
otherwise read the README will in this case, as it is the only file in
|
||||
the repository.
|
||||
|
||||
Step 4: Remove Project from Infrastructure Systems
|
||||
Step 3: Remove Project from Infrastructure Systems
|
||||
--------------------------------------------------
|
||||
|
||||
Once your repository is in its final state, prepare a second change to
|
||||
|
|
@ -459,15 +452,6 @@ following:
|
|||
team to restore the project status back to "Active" in Gerrit before ACLs
|
||||
can be reapplied successfully.
|
||||
|
||||
Step 5: Remove Repository from the Governance Repository
|
||||
--------------------------------------------------------
|
||||
|
||||
If this was an official OpenStack project, remove it from the
|
||||
``reference/projects.yaml`` file and add it to the file
|
||||
``reference/legacy.yaml`` in the ``openstack/governance`` repository.
|
||||
Note that if the project was recently active, this may have
|
||||
implications for automatic detection of ATCs.
|
||||
|
||||
Package Requirements
|
||||
====================
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue