Open
Conversation
move version info out to `version.h` file version info now a semantic version, with major, minor, patch, and “candidate” info, as well as an indicator for candidate type (displayed if candidate number is non-zero) support for showing an automatically-generated build number added, which can be provided by a build script and is intended to be derived from the git hash with this approach it should also be possible in the future to add other tooling to automatically increment version numbers version info also includes the codebase variant, allowing us to easily differentiate between Quark and Console8
Owner
|
I'll switch to this after 1.04 has been released properly, save confusing everyone (including myself) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've moved the AgonConsole8 fork of agon-vdp to use semantic versioning.
There's several reasons why. On other projects I've used CI tooling that will do things like automatically increment version numbers and create new releases when new commits get pushed to
main, and at some point I'd like to implement that.Another reason is that I think it would be good for us to make more frequent releases. By having "major.minor.patch" it feels like the stakes are lower for cutting a new release that contains only patch changes. It's also not such a big deal to add in new minor features.
This PR sets the version at "2.0.0 Alpha 1". This is a straw-man number. Given that there has been quite a lot of changes made since the last full release, and this moves to a new version numbering system it feels like a justifiable number.
From the commit message:
move version info out to
version.hfile.version info now a semantic version, with major, minor, patch, and “candidate” info, as well as an indicator for candidate type (displayed if candidate number is non-zero)
support for showing an automatically-generated build number added, which can be provided by a build script and is intended to be derived from the git hash
with this approach it should also be possible in the future to add other tooling to automatically increment version numbers
version info also includes the codebase variant, allowing us to easily differentiate between Quark and Console8