Validating a release candidate

The release candidate (RC) is the build the team treats as final, subject to validation. The RC phase is the last line of defense before users see changes — where scope discipline and test coverage matter most.

Scope freeze

From RC onward, only critical bug fixes enter. Any new feature slips to the next version. That freeze must be communicated clearly to engineering, product, and stakeholders — ideally tied to a tagged build and release object.

Validation battery

Full regression, real-device testing, store content review, release notes proofread. The HyperRelease checklist captures these validations so nothing is “assumed done” because someone said so in chat.

Promoting RC to release

When validations pass, the RC becomes the official release. Status moves to Ready on each platform, then Published after store submission or deployment — with a clear audit trail of who approved the promotion.

In summary

The RC is not a formality — it is the quality filter. HyperRelease structures that critical phase.