Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update repo RM role policy regarding EOL branches #1483

Merged
merged 2 commits into from
Jan 10, 2025
+3 −3
Merged

Update repo RM role policy regarding EOL branches #1483

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47cb63b
Update repo RM role policy regarding EOL branches
hugovk Jan 9, 2025
1fc0c0f
Improve wording
hugovk Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions developer-workflow/development-cycle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,9 +363,9 @@ Repository release manager role policy
Release Managers for :ref:`in-development <indevbranch>`, :ref:`maintenance
<maintbranch>`, and :ref:`security mode <secbranch>` Python releases are
granted Administrator privileges on the repository. Once a release branch has
entered :ref:`end-of-life <eolbranch>`, 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 <eolbranch>`, 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.
Expand Down
Loading