Skip to content

docs(governance): add release manager role (#1558) #1746

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

Merged
RUKAYAT-CODER merged 2 commits into from
Sep 30, 2026
Merged

docs(governance): add release manager role (#1558) #1746

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6f34204
docs(governance): add release manager role (#1558)
MerlinTheWhiz Sep 30, 2026
6de252f
Merge branch 'main' into chore/issue-1558-release-manager-role
RUKAYAT-CODER Sep 30, 2026
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
19 changes: 19 additions & 0 deletions Governance/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ Entries are added newest-first. Format: date · version · summary · pull reque

| Date | Version | Change | PR |
| ---------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
| 2026-09-30 | 1.0.0 | Added `roles/RELEASE_MANAGER.md` — release duties, sign-off authority and its limits, and a per-release rotation (issue #1558). | This pull request |
| 2026-09-30 | 1.0.0 | Added `processes/ONBOARDING.md` — onboarding ownership, phased steps, and the resources a new contributor receives (issue #1565). | This pull request |
| 2026-09-28 | 1.0.0 | **Initial release.** Added `policies/COMMUNICATION_NORMS.md` and created the `Governance/` tree. Covers tone and etiquette, official channels, and response-time expectations. | This pull request |

Expand Down Expand Up @@ -204,6 +205,24 @@ Standalone process documents live in `Governance/processes/`:
- [`processes/ESCALATION_PATH.md`](processes/ESCALATION_PATH.md) — incident escalation tiers, role-based contacts, and response SLAs.
- [`processes/WORKING_GROUP_DISSOLUTION.md`](processes/WORKING_GROUP_DISSOLUTION.md) — dissolution triggers, artifact handover, and archival steps for working groups.

## Roles

Role definitions live in `Governance/roles/`. They describe what a role is
responsible for, not how to reach it — progression between the core community
roles follows [`processes/PROMOTION_CRITERIA.md`](processes/PROMOTION_CRITERIA.md).

- [`roles/CONTRIBUTOR.md`](roles/CONTRIBUTOR.md) — who a contributor is, the rights
the role grants, and how a person becomes one.
- [`roles/MAINTAINER.md`](roles/MAINTAINER.md) — maintainer responsibilities,
review and merge authority, and accountability.
- [`roles/TREASURER.md`](roles/TREASURER.md) — community treasury custody,
spending authority limits, and reporting obligations.
- [`roles/RELEASE_MANAGER.md`](roles/RELEASE_MANAGER.md) — release duties, sign-off
authority and its limits, and the per-release rotation. A delegated functional
appointment held by a maintainer, sitting outside the promotion ladder; final
release authorization stays with the lead maintainer per
[`processes/RELEASE_SIGNOFF.md`](processes/RELEASE_SIGNOFF.md) §4.

## Templates
Reusable templates live in `Governance/templates/`:
- [`templates/RELEASE_CHECKLIST.md`](templates/RELEASE_CHECKLIST.md) — the
Expand Down
Loading
Loading