vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-05-02 13:30:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

Close RC-era issue gaps blocking v6 GA

Browse source 
Refs #1430

Refs #1436

Refs #1435

Refs #1409

Refs #1429

Refs #1432
This commit is contained in:
rcourtman 2026-04-21 14:46:23 +01:00
parent ee2537987f
commit fd5c14b049
23 changed files with 657 additions and 166 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md
View file

@ -94,7 +94,10 @@ Cloud, and self-hosted production users.
4. Every stable promotion requires:
- Applicable items in `PRE_RELEASE_CHECKLIST.md` complete.
- Applicable entries in `HIGH_RISK_RELEASE_VERIFICATION_MATRIX.md` cleared.
- No known unresolved high-severity regressions in touched release surfaces.
- No known unresolved RC-era user-visible issues intended for the v6 GA
scope remain open. Each one must be fixed in the candidate, proven
invalid with evidence, or conservatively superseded with the original
failure resolved or explicitly narrowed.
- The previous stable rollback target and exact reinstall command recorded.
- A live release-pipeline exercise already completed for the promoted prerelease tag,
not only YAML lint or static workflow validation.
@ -156,6 +159,9 @@ Cloud, and self-hosted production users.
locked in the launch ticket before promotion: preview deploy/audit commands,
production deploy/audit commands, and the explicit rollback deploy/audit
commands that return `pulserelay.pro` to the approved v5 posture.
10. For v6 GA, attach the dated RC issue-closure record for the candidate so
the final issue set and its dispositions are explicit in the promotion
packet rather than implied.
## Authority