docs: define PR acceptance and release process

This commit is contained in:
Joseph Magly
2026-08-23 13:45:56 -04:00
parent d4bd372512
commit 8e998fc842
6 changed files with 149 additions and 6 deletions
+6
View File
@@ -12,6 +12,12 @@ days, and treats evidence older than eight days as stale. Every workflow run pub
a summary showing selected, successful, failed, and not-selected/no-fresh-evidence
gates.
For a release, maintainers run the applicable hosted software gates manually against
the exact signed tag before publication. Publishing the release triggers the same
workflow again, and that release-event run is retained as the final freshness record.
Unselected hardware or credential-bound jobs remain explicit non-evidence. See
[`RELEASE_PROCESS.md`](RELEASE_PROCESS.md) for their place in the release sequence.
Unavailable hardware or credential-bound gates may use a committed environment
waiver for at most 30 days. Each waiver names one gate, a canonical tracking issue,
the reason, its opening and expiry dates, and the support claim it blocks. Invalid,