From eb1fbc4ffb72b692b5b841cef904aebaa883c521 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Fri, 10 Jan 2025 19:53:48 +0200 Subject: [PATCH] Update repo RM role policy regarding EOL branches (#1483) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- developer-workflow/development-cycle.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 9beb8cb04..8a37692ad 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -363,9 +363,9 @@ Repository release manager role policy Release Managers for :ref:`in-development `, :ref:`maintenance `, and :ref:`security mode ` Python releases are granted Administrator privileges on the repository. Once a release branch has -entered :ref:`end-of-life `, the Release Manager for that branch is -removed as an Administrator and granted sole privileges (out side of repository -administrators) to merge changes to that branch. +entered :ref:`end-of-life `, the Release Manager for that branch +creates a final tag and deletes the branch. After this, they are +removed as an Administrator. Multi-Factor Authentication must be enabled by the user in order to retain access as a Release Manager of the branch.