Add RELEASE.md for beta, stable, verification, and rollback workflow
Open
@mehul0810 is already working on this.
Since Jul 7, 2026.
area: build-ci
area: docs
priority: medium
status: ready
type: maintenance
- Dominant language
- PHP
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The repo does not have a dedicated RELEASE.md that documents Perform prerelease and stable-release execution, verification, and rollback rules.
Evidence
- Repo-root audit found no
RELEASE.md. - Recent 1.7.0 beta work required ad hoc coordination for tag naming, asset hashing, prerelease notes, stable-line protection, and post-release verification.
Scope
- Add
RELEASE.mdfor beta and stable release flow. - Document branch/tag conventions, asset packaging, release-note expectations, and post-release verification.
- Define what must stay unchanged during beta work, including stable GitHub release and WordPress.org stable line.
- Include rollback expectations and immediate post-release monitoring steps.
Acceptance criteria
- One canonical release operations doc exists in the repo root.
- Beta vs stable actions are separated clearly.
- Tag, asset, release-note, and verification steps are documented.
- The doc makes hard gates and owner approvals explicit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.