Skip to content

docs(contributing): review asked the backup to approve every maintainer PR - #150

Merged
jamesconwaydev merged 1 commit into
mainfrom
docs/release-review
Nov 3, 2026
Merged

jamesconwaydev merged 1 commit into
mainfrom
docs/release-review

Conversation

@jamesconwaydev

Copy link
Copy Markdown
Owner

The backup maintainer is there for continuity, not day-to-day review. This moves the maintainer's second reader to release time: the backup reviews the release PR, which carries every change since the last tag, and the tag waits for that approval. Contributor PRs are still reviewed by the maintainer before they merge. Security fixes can ship first and be reviewed afterwards.

…er PR

The backup maintainer is there for continuity, not day-to-day review.
Maintainer PRs now get their second reader once per release: the backup
reviews the release PR, which carries every change since the last tag,
and the tag waits for that approval. Security fixes can ship first and
be reviewed afterwards.

Signed-off-by: James Conway <148910373+jamesconwaydev@users.noreply.github.com>
@jamesconwaydev
jamesconwaydev merged commit 3bbf52c into main Nov 3, 2026
6 checks passed
@jamesconwaydev
jamesconwaydev deleted the docs/release-review branch November 3, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant