RCbased

Rcbased, sometimes written rc-based, is a term used in software development to describe a workflow in which release candidates serve as the central baselines for testing, integration, and deployment. In a rcbased approach, development progresses toward a series of RC builds derived from the mainline before a final release. Version strings commonly include an RC identifier (for example, 3.4.0-rc.2). RC builds are subjected to targeted QA, performance testing, and user acceptance testing, with the intent of uncovering issues before the final release.

Implementation typically involves creating an RC branch or tagging an RC in the version control system, configuring CI pipelines to publish RC artifacts, and maintaining release notes that enumerate changes since the previous release. The RC window may have rules about what changes are permitted and how long the RC phase lasts. Once testing is satisfactory, the RC is promoted to a final release; otherwise issues trigger corrective updates and a new RC.

Adoption of rcbased practices varies by project and ecosystem. It is common in large software projects and some open-source communities that value early and iterative feedback. Benefits include earlier QA feedback, clearer stabilization timelines, and reduced post-release hotfix risk. Potential drawbacks include longer release cycles, the overhead of maintaining multiple RC builds, and possible confusion around versioning if conventions are not consistently followed.

See also: release candidate, semantic versioning, continuous delivery, release management.