Release candidate

Short Definition

A release candidate is a near final software version prepared for final testing before it becomes an official release.

Extended Definition

A release candidate (RC) represents a build that is feature complete and has passed most tests but still requires validation under realistic conditions. It is often used to evaluate readiness for production. Release candidates allow teams to check for unexpected issues, integration problems, performance regressions, or user experience concerns before declaring a stable version.

An RC phase acts as a safety buffer. Instead of pushing a major release directly, teams use release candidates to catch late-stage issues, confirm stability, and finalize documentation or migration notes.

Deep Technical Explanation

Release candidates have defined characteristics.

Feature complete

No new features are introduced. Only critical fixes may be added before the final release.

Versioning

RC versions typically follow semantic versioning conventions:

2.0.0 rc.1
1.4.5 rc.3

These versions signal to consumers that the build is almost stable.

Release readiness validation

Teams perform extensive validation:

Full regression testing
Performance and load checks
API compatibility verification
Database migration rehearsal
Security scanning and dependency review

Lockdown phase

Once the RC is published, the release is frozen except for critical patches.

Promotion

If the release candidate shows no blocking issues, it becomes the final release. If problems arise, a new RC is created.

Practical Examples

Preparing 3.0.0 rc.1 to validate a large API update
Testing an RC in staging with production-like traffic
Running final load tests to detect regressions
Publishing an RC to internal users for feedback before launch

Why It Matters

Release candidates help organizations prevent high-risk releases. They serve as a safe checkpoint before exposing new versions to all users. RCs reduce emergency hotfixes, improve user trust, and ensure smooth deployments.