From 90982cdbfbec673597899c61e5fa667f00b3e03e Mon Sep 17 00:00:00 2001 From: Brian Rosmaita Date: Tue, 14 Nov 2023 15:25:34 -0500 Subject: [PATCH] Resolution to create openstack-unmaintained core This patch proposes an amendment to the 2023-07-24 "Unmaintained status replaces Extended Maintenance" resolution to allow an openstack-wide group to handle Unmaintained branch changes across all projects by default, though this can be overridden by individual projects. Additionally, the original resolution file has been modified to include a note that the amendment exists along with a link to it. Change-Id: Iecc9751091285a5d3ca72c8d959136b33e274839 --- .../20230724-unmaintained-branches.rst | 12 ++++++ .../20231114-amend-unmaintained-status.rst | 39 +++++++++++++++++++ 2 files changed, 51 insertions(+) create mode 100644 resolutions/20231114-amend-unmaintained-status.rst diff --git a/resolutions/20230724-unmaintained-branches.rst b/resolutions/20230724-unmaintained-branches.rst index 1dc957252..b992eb008 100644 --- a/resolutions/20230724-unmaintained-branches.rst +++ b/resolutions/20230724-unmaintained-branches.rst @@ -2,6 +2,12 @@ 2023-07-24 Unmaintained status replaces Extended Maintenance ============================================================= +.. note:: + This resolution has been amended by + :doc:`20231114-amend-unmaintained-status`. + See :ref:`the amendment note<20231114-amend-note>`, below. + + Motivation ---------- @@ -54,6 +60,12 @@ around the responsibilities and defining clearer processes. Unmaintained branches --------------------- +.. _20231114-amend-note: + +.. note:: + The fourth point below has been amended by a subsequent resolution. + See :doc:`20231114-amend-unmaintained-status` for details. + - The phase of Extended Maintenance for a branch is renamed to Unmaintained. - Only SLURP releases are eligible for having an Unmaintained branch. - After a branch is no longer officially maintained, the branch is deleted and diff --git a/resolutions/20231114-amend-unmaintained-status.rst b/resolutions/20231114-amend-unmaintained-status.rst new file mode 100644 index 000000000..74687627b --- /dev/null +++ b/resolutions/20231114-amend-unmaintained-status.rst @@ -0,0 +1,39 @@ +===================================================== + 2023-11-14 openstack-unmaintained-core Gerrit Group +===================================================== + +Amendment +--------- + +The resolution :doc:`20230724-unmaintained-branches` contains the following +text in the "Unmaintained branches" section: + +- A group in Gerrit called "-unmaintained-core", for example, + "keystone-unmaintained-core", will have +2/+W on these branches. This group + may be bootstrapped with or include the "-stable-maint" group, but + membership is separate from that group. + +The above point is hereby replaced by the following two points: + +- A group in Gerrit called "openstack-unmaintained-core" will by default have + +2/+W on these branches for all projects. This group will be self-managed + and will be owned by the OpenStack Technical Committee. The Technical + Committee will only have the ability to maintain group membership; TC + members will not be members of openstack-unmaintained-core through their + membership in the TC. + +- Each individual project team has the option to create a group in Gerrit + called "-unmaintained-core", for example, + "keystone-unmaintained-core", that has +2/+W solely on that project's + "unmaintained/\*" branches. This group may be bootstrapped with or include + the "-stable-maint" group, but membership is separate from that + group. Further, this group may override the powers of the + openstack-unmaintained-core group for the project's Unmaintained branches. + +Effect of this Change +--------------------- + +- There is an OpenStack-wide group with the responsibility to handle branches + in Unmaintained status across all projects. +- It is possible for individual project teams to override the OpenStack-wide + group for that project's Unmaintained branches.