Commit Graph

315 Commits

Author SHA1 Message Date
Elod Illes 8f25583cab Add NOTE about becoming Unmaintained core team member
Change-Id: I487c59c3b2f580e2fd6f6d56c4eeaa5a23119602
2024-03-01 18:00:50 +01:00
Zuul 7cc5e309c3 Merge "Update docs for Unmaintained" 2024-02-02 18:46:44 +00:00
Kristi Nikolla 2594b26ad5 Update docs for Unmaintained
Updates the Stable Branches page of the project team guide to
describe Unmaintained branches[0, 1].

[0] https://review.opendev.org/c/openstack/governance/+/888771
[1] https://review.opendev.org/c/openstack/governance/+/900940

Change-Id: I2171e5b82a15dc6462410b8fc6ecfe444b42ae10
2024-01-19 18:30:31 -05:00
Takashi Kajinami 7f58997b24 Add note about official-openstack-repo-jobs template
The official-openstack-repo-jobs template should be kept during
repository retirement process to sync updates to GitHub mirrors.

Change-Id: Ib1fdc4c805a62d04f8cdbcedd5fcafd7ab69a79e
2024-01-19 01:30:55 +09:00
Brian Rosmaita d15861b2ff Clarify deliverable retirement step
This is a followup to some comments on change I84490c186f2d.

Change-Id: Id28612546e5551765c624d2964e41dbdd1a3ab22
2024-01-12 12:08:38 -05:00
Brian Rosmaita 8108b04868 Update repo deprecation instructions
Add a step to remove a deliverable's yaml file from the
openstack/releases repository when a project is deprecated.

Change-Id: I84490c186f2d39dc2ab01fbbc63a4bb880e24d93
2024-01-11 16:51:18 -05:00
Zuul d141bcafff Merge "Add call for Extra AC in PTL guide" 2023-09-14 17:32:32 +00:00
renliang 0bc374d381 Add and remove incorrect links
Change-Id: Idd16e92c2ddd0b3571275dd52777422a2af320fd
2023-09-13 09:51:21 +08:00
Ghanshyam Mann c2e00c48fb Add call for Extra AC in PTL guide
In TC meeting[1], we discussed about how to
notify community to add for the extra AC. In
every election, we need to call for adding the
extra-AC. Adding this a one of the task for PTL
so that they remind to propose the extra AC of
their project.

[1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-09-05-18.01.log.html

Change-Id: I9cd2ab4724dad5a30f551fe3a728b2a06f775cc0
2023-09-12 19:10:45 +00:00
Brian Rosmaita fa6f40684c Add SLURP release notes strategy
The aim of this patch is:
- make clear what the TC suggests doing
- make clear why the TC thinks it should be done this way
- give a helpful example of how to do it

Change-Id: I90b7600866d0d99b5cfccecb2bda9f2505ef4b27
2023-08-01 17:38:43 -04:00
Ghanshyam Mann e8a3a7eb96 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
2023-04-10 17:49:09 -05:00
Dmitriy Rabotyagov 824304d561 Clarify project deprecation guide
Some steps are not clear enough and requires to do extra research or
educated guesses on what is exactly meant in a specific step. This patch
aims to clerify required steps - what repository and what files should be
changed to get project deprecated. Also some generic cleanup made.

Change-Id: I8a749acbd2b26327114ef76d4e79c06c3ed5b8c6
2022-10-31 16:50:22 +01:00
Ghanshyam Mann 1246dcbb32 Clarify Extended Maintenance branch testing and support policy
We at upstream community cannot commit to the maintenance of
Extended Maintenance branches and its testing. Idea behind the
Extended Maintenance is to keep them open as long as we can and
anyone backporting the fixes take care of tetsing fix or so.

Change-Id: Ide5d13139493737e5ce948b62cd1da9aad7022c7
2022-10-13 10:58:44 -05:00
Zuul 7cbeb0de40 Merge "Explicitly mention the each steps of repo retirement" 2022-10-06 15:13:09 +00:00
Ghanshyam Mann 4df577d376 Add openstack-map and zuul jobs updates step in repository handling
While renaming or retiring repository, we usually forget to update the
openstack-map and zuul jobs definition. To remind to do those, let's
explicitly add these steps in repository rename/retire process.

Change-Id: I8fd68f1ef4b4b1307d9f5fa3023f0a7544186268
2022-09-29 14:08:53 -05:00
Zuul 1230e41276 Merge "remove unicode from code" 2022-08-30 11:32:48 +00:00
niuke ded18750a3 remove unicode from code
Change-Id: Ifb9d1b07eef84bfe01eea74f5eb590421a2a86ad
2022-07-28 08:51:43 +08:00
Brian Rosmaita 32eea0cf49 Add Legal Issues FAQ
Bring the wiki page content under version control and incorporate
it into the Project Team Guide.

Change-Id: Ieb66c48aa420b9c3920e503376f260456dff3ad9
2022-07-21 12:38:49 -04:00
Ghanshyam Mann f35460edcb Explicitly mention the each steps of repo retirement
In repo retirement process, we need to wait for
governance patch to get TC agreement as well as to check
the proper retirement which need repo content removal first
to check the proper retirement. But as we refer to the OpenDev
manual for 3 steps together, this become confusing to mention the
right order. As per OpenStack process, those 3 steps need to be in
different order.

We have note about those but still it may confuse people to know
the right order.

I am extracting the each step explictly and what patch they need
to depends-on.

Change-Id: Ie932b38c79eaa5947959c6f642c041acfdb87679
2022-04-28 12:57:31 -05:00
Zuul c3eca383d8 Merge "Fix the dependency hierarchy in repo retirement process" 2022-04-28 12:55:09 +00:00
Daniel Pawlik 9434b08999 Add information for checking status of other job results
The Opensearch is storing most part of the Zuul CI job results
log files that can be useful for developers.

Change-Id: I3c79cdb7132c60595fe3fa5a46ec1c778db1d34e
2022-04-20 08:21:44 +02:00
Ghanshyam Mann 35d84b0967 Fix the dependency hierarchy in repo retirement process
In repo retirement steps, governance patch needs to wait until
repo content is removed. Fixing that step in doc.

Change-Id: I525f3c7ec21ddf64922cf785c3fdc15bc93f9f49
2022-04-13 19:40:33 -05:00
Dan Smith b6b26faefe Revise the tick deprecation example
As discussed in the PTG, the tick deprecation example was too
aggressive in its requirements for notice, requiring more notice
time than we require today. This was not the intent, so this corrects
that to the expected timeline.

Change-Id: I241cf3723312b299697a44ee43cc8aeadfadadd7
2022-04-12 11:52:56 -07:00
Dan Smith ef313d1f8e Add generic guidance on rechecks
Per recent discussions, this attempts to provide some general
guidance about responsible use of rechecks that we can link to when
"encouraging" people to exhibit the desired behavior.

Change-Id: Iadfc32f79423b54e5933788686791c42c8d616fd
2022-04-05 07:42:32 -07:00
Zuul f4f4325a0a Merge "Update note about periodic jobs" 2022-04-04 14:35:09 +00:00
Zuul 2335337fd6 Merge "Move the projects list following the stable branch policy" 2022-04-04 14:34:50 +00:00
Zuul b8c39c3ba2 Merge "Modify the project specific stable team management" 2022-04-04 14:29:50 +00:00
Brian Rosmaita 2876008419 Update note about periodic jobs
Update the note to refer to zuul instead of jenkins.

Change-Id: I830d81a272cafaff64f69f06ec4d2a36e3381a6c
2022-04-01 18:21:30 -04:00
Ghanshyam Mann cce6bc4bf4 Move the projects list following the stable branch policy
TC is removing the tag framework. Stable policy tag has the
list of projects following the stable branch policy
- https://governance.openstack.org/tc/reference/tags/stable_follows-policy.html#application-to-current-deliverables

Moving that list to stable branch policy doc which will be
helpful to know the projects following the polic.

Change-Id: Ic28b9534f0432bf1ba1f24bbe0582e6aa68223de
2022-04-01 15:37:24 -05:00
Ghanshyam Mann 104ecfdf2c Modify the project specific stable team management
In Xena, TC passed the resolution about enabling the
project team manage their stable core team.
- https://governance.openstack.org/tc/resolutions/20210923-stable-core-team.html

This commits relfects that resolution in stable branch
policy document.

Change-Id: I43d41cd9a1e0af0b0f2e4fc145f97c3ff4f76f8e
2022-04-01 15:10:58 -05:00
Zuul 9c6f5f70f2 Merge "Update repository handling document" 2022-04-01 19:21:42 +00:00
Ghanshyam Mann b1d1a63742 Update repository handling document
Sometime it is confusing whether to merge the
repo retirement/deprecation in governance and then
start the code/infra cleanup or other way around.
Usually all code/infra cleanup patches check if
there is patch submitted in governance or not.

If there is objection by TC or by any reasonTC decided
not to approve the repo retirement/deprecation then code/infra
cleanup including the project rename revert will be very costly.

To make it the process clear and in right sequence, updating the
document to merge the governance patch first and then start the
other steps.

Change-Id: I5c911f9dde8e4244156ad79898299dc3f0a11460
2022-03-31 22:12:59 -05:00
Ghanshyam Mann ba41eb0c7a Move technical-guidance.rst under technical-guides
We have new directory technical-guides which include
the new guidlines unified limits. We can move the existing
file technical-guidance.rst also under the same dir to
avoid any confusion.

Change-Id: Ibe9facc4518b1f1317579373b40a5e63f89d2240
2022-03-22 20:20:49 -05:00
Dan Smith 0e28af9708 Amend unified-limits technical guide
This encapsulates the feedback received after the base document
merged.

Change-Id: I02b41ed76eefac700ad2d9dc464a4ef878d403d6
2022-03-16 08:39:05 -07:00
Dan Smith ee9ddbc45c Add unified-limits technical guide
Change-Id: Idf462dd253c51e2bc8baa57f7b33865892266e7e
2022-03-15 15:21:12 -07:00
Dan Smith 1b3ba23cb3 Migrate deprecation tag to a document here
This moves the guidelines of how feature deprecation should be handled
from the definition of assert:follows-standard-deprecation tag to
a document here. It reformats the verbiage therein to describe the
procedures as a guideline instead of adherence to an asserted tag. It
also modifies the procedures to be in line with the newly-adopted
TC resolution to modify the release cadence with tick and tock
designations which impact the timing of deprecations and feature
removals.

Change-Id: I9e6b252e81f893e0007c5b917328b73765d072c7
2022-03-09 09:54:11 -08:00
zhangbailin 9a0340764f Redirect to the correct hyperlink
https://www.stackalytics.com/ has already changed to
https://www.stackalytics.io/, this patch update the hyperlink with
stackalytics.

Change-Id: If5fa5dd8aa3802c614c09f37c88bbebc37f542be
2022-01-20 15:28:04 +08:00
Mohammed Naser 5e4eeade64 Improve docs wrt generate-constraints
The command seems to be out of date and there is a tox
target that already takes care of it with an up to date command
so let's instruct developers to use that.

Change-Id: I0848248e21dfc23466310ff1996f898f270dd12c
2021-12-05 09:42:41 +04:00
Zuul 0c17dd4a7c Merge "Remove 'Unmaintained' phase" 2021-09-28 21:59:35 +00:00
Zuul 79aa724a71 Merge "Document about using publish-to-pypi-stable-only for deprecated repo" 2021-09-25 15:59:16 +00:00
Zuul 6647e0a9c2 Merge "Added spread-the-word.rst" 2021-09-25 15:52:40 +00:00
Amy Marrich (spotz) a5e964509f Added spread-the-word.rst
Added Spread the word page from the Xena TC Initiatives

Change-Id: I437e98c1653c7c2873e7d74ce8568de855324fc0
2021-09-24 09:16:15 -05:00
Zuul e29e9b543b Merge "Tag deliverables as retired" 2021-09-23 22:43:45 +00:00
Elod Illes b9c16396d6 Remove 'Unmaintained' phase
During Xena Virtual PTG on the Technical Committee session there was a
discussion, that the 'Unmaintained' phase is not really clear for the
community and just creates confusion. The decision was to simply remove
this phase as the process is more clear and works well without it.

Change-Id: I9589cbdd74d83d23ad42ce6724e3b8e4cc56c44d
2021-09-22 20:08:30 +02:00
Rajat Dhasmana 0a0dcda79b Add section regarding releasing stable branches
This patch adds a section with guidelines regarding releasing stable
branches.

Change-Id: Id8d86f78cb35c679df330b5132f7704cb87e07bb
2021-09-15 12:51:55 -04:00
Ghanshyam Mann 211f3d4c70 Document about using publish-to-pypi-stable-only for deprecated repo
We have a new tempest publish-to-pypi-stable-only now which is
used for the deprecated repo which still support stable branches.

This commit document it in project-team-guide.

Ref: https://review.opendev.org/c/openstack/project-config/+/800558
Change-Id: If4c73fe6a32f9e2a4f9841ab67aab05f7d76f6d3
2021-07-22 14:16:23 +00:00
Hervé Beraud 1c84fd3d1f Tag deliverables as retired
From the release team point of view we need to ensure that deliverables are
well tagged as retired to ensure that our machinery will work as
expected all along the series life cycle.

Here is an example of experienced problem with your validation:

https://review.opendev.org/c/openstack/releases/+/792820/5..6

Change-Id: I6cb59e7cc09bd6a8cda0ffe06ffcd896696aea86
2021-06-16 17:00:33 +02:00
Ghanshyam Mann 14732bd7be Modify the meeting channel preference
As discussed during the migration from IRC freenode to
OFTC[1], TC encourage project team to hold their meeting
on their project channel.

Updating project team guide to reflect that.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022718.html

Change-Id: I6c58ff14402238b067a093e6d3974cbb5faf3b1b
2021-06-11 16:29:54 +00:00
Zuul de93da90d3 Merge "Required Updates for TC and UC merge" 2021-06-07 09:12:56 +00:00
Ghanshyam Mann fc365df187 Required Updates for TC and UC merge
UC has been merged into TC since June 2020, this
commit clarify it in project team guide docs and
remove the explicit reference of old committee.

Change-Id: I5c5fe7ec5121f6429ec7d198f88cb72d18204769
2021-06-05 13:18:50 +00:00