Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix version and update docs for proper version management #890

Merged
merged 2 commits into from
Oct 7, 2024
Merged

Fix version and update docs for proper version management #890

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cbebf87
Move ngen build project to "current" version.
robertbartel Oct 7, 2024
13b4720
Clarify steps in release management doc.
robertbartel Oct 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CMakeLists.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ set(CMAKE_CXX_STANDARD_REQUIRED True)
set(CMAKE_CXX_VISIBILITY_PRESET hidden)

# Define project version and use via generated config header
project(ngen VERSION 0.1.0)
project(ngen VERSION 0.2.0)

add_executable(ngen "${NGEN_SRC_DIR}/NGen.cpp")

Expand Down
5 changes: 4 additions & 1 deletion doc/RELEASE_MANAGEMENT.md
View file
Open in desktop
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
Loading