Skip to content

Commit

Permalink
Clarify steps in release management doc.
Browse files Browse the repository at this point in the history
  • Loading branch information
robertbartel authored and christophertubbs committed Oct 7, 2024
1 parent cdce746 commit 61bcbad
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion doc/RELEASE_MANAGEMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,10 @@ The release process can be summarized fairly simply:
- Version numbering should follow [Semantic Versioning](https://semver.org/) and its typical `MAJOR.MINOR.PATCH` pattern
2. A release candidate branch, based on `master`, is created in the official OWP repo
- The name of this branch will be `release-X` for version `X`
3. All necessary testing and quality pre-release tasks are performed using this release candiate branch
3. The version is incremented in the main [CMakeLists.txt](../CMakeLists.txt)
- Update the line setting the version, which will look something like `project(ngen VERSION x.y.z)`
- Then committed and pushed this change to the `release-X` branch
4. All necessary testing and quality pre-release tasks are performed using this release candidate branch
- **TODO**: to be documented in more detail
4. (If necessary) Bug fixes, documentation updates, and other acceptable, non-feature changes are applied to the release branch
- Such changes should go through some peer review process before inclusion in the official OWP branch (e.g., PRs, out-of-band code reviews, etc.)
Expand Down

0 comments on commit 61bcbad

Please sign in to comment.