Repository navigation
Change versioning scheme to <package>+<upstream> - #26
Merged
Merged
Conversation
An include guard is unecessary since this file will never be included by any C files.
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
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.
This PR changes our versioning scheme to match the one used by allyourcodebase/SDL:
<package>+<upstream>. Using this scheme allows us to clearly track the package version and upstream versions separately. We can make releases withbuild.zigpatches without having to wait for an upstream release.This change will take effect in the next (soon to be) release. I don't expect it to break anyone's code.
CC @MasonRemaley if you have any thoughts. Thanks for the clever version scheme!