Fix version in maven central and follow SEMVER requirements #167
Conversation
This file contains 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
up-java pre-dates open sourcing uProtocol. Initial releases to maven central took on the up-spec version numbering which led to confusion as the patch number of up-java wasn't a direct correlation with the specifications. The decision was made (to fast) to then switch to 0.x.x for up-java however this further confused folks who go to maven central and see that v0.x is newer than v1.x. To clean this up, we will switch up-java to version 2.x.x and moving forward, we will follow SEMVER requirements for major, minor, and patch updates. #166
|
Code coverage report is ready! 📈
|
neelam-kushwah
approved these changes
Jul 25, 2024
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.
up-java pre-dates open sourcing uProtocol. Initial releases to maven central took on the up-spec version numbering which led to confusion as the patch number of up-java wasn't a direct correlation with the specifications. The decision was made (to fast) to then switch to 0.x.x for up-java however this further confused folks who go to maven central and see that v0.x is newer than v1.x.
To clean this up, we will switch up-java to version 2.x.x and moving forward, we will follow SEMVER requirements for major, minor, and patch updates.
#166