Git Release Candidate Branch
A Git Release Candidate Branch is a version-specific stabilization code version control branch that prepares git release candidate major version releases with the naming pattern `rc/<project>-<version>`.
- AKA: Git RC Branch, Release Preparation Branch, Version Candidate Branch, Pre-Release Branch.
- Context:
- It can typically merge from Git Development Branches through git release candidate integration processes.
- It can typically undergo Git Release Candidate Testings through git release candidate quality assurances.
- It can typically merge to Git Master Branches through git release candidate promotion processes.
- It can often include Git Release Candidate Bug Fixes through git release candidate stabilization changes.
- It can often exclude Git Release Candidate Feature Additions through git release candidate feature freezes.
- It can often trigger Git Release Candidate Builds through git release candidate deployment preparations.
- ...
- It can range from being a Quick Git Release Candidate Branch to being an Extended Git Release Candidate Branch, depending on its git release candidate stabilization period.
- It can range from being a Minor Git Release Candidate Branch to being a Major Git Release Candidate Branch, depending on its git release candidate version scope.
- It can range from being a Stable Git Release Candidate Branch to being an Unstable Git Release Candidate Branch, depending on its git release candidate quality level.
- It can range from being a Feature-Complete Git Release Candidate Branch to being a Partial Git Release Candidate Branch, depending on its git release candidate feature readiness.
- It can range from being a Internal Git Release Candidate Branch to being a Public Git Release Candidate Branch, depending on its git release candidate visibility scope.
- ...
- It can enforce Git Release Candidate Version Lock for git release candidate dependency management.
- It can maintain Git Release Candidate Changelog for git release candidate documentation.
- It can require Git Release Candidate Sign-off for git release candidate approval process.
- It can generate Git Release Candidate Artifact for git release candidate distribution.
- It can coordinate Git Release Candidate Rollback Plan for git release candidate risk mitigation.
- ...
- Examples:
- Semantic Version Git Release Candidate Branches, such as:
- Major Version Git Release Candidate Branch (rc/project-2.0.0) with git release candidate breaking changes.
- Minor Version Git Release Candidate Branch (rc/project-1.5.0) with git release candidate feature additions.
- Patch Version Git Release Candidate Branch (rc/project-1.4.3) with git release candidate bug fixes.
- Environment-Targeted Git Release Candidate Branches, such as:
- Platform-Specific Git Release Candidate Branches, such as:
- ...
- Semantic Version Git Release Candidate Branches, such as:
- Counter-Examples:
- Git Development Branch, which accepts git unstable changes rather than git release stabilization.
- Git Feature Branch, which implements git new functionality rather than git release preparation.
- Git Hotfix Branch, which addresses git emergency issues rather than git planned releases.
- See: Git Branching Strategy, Git Master Branch, Git Development Branch, Software Release Management, Version Control System, Continuous Delivery Practice, Quality Assurance Process, Deployment Pipeline, Semantic Versioning.