-
Notifications
You must be signed in to change notification settings - Fork 156
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.
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
Use semantic versioning? #465
Comments
If I recall correctly, the original PvPGN developers wanted PvPGN 2.0 to become a general server software for all kinds of games, so they versioned their ongoing rewrite as As you can see now, the Why? Because updating the major version to 2 without implementing the aforementioned goal would go against the original developers' wishes. We could make the version number more pretty by slightly deviating from the Semantic Versioning specification by forever updating just the minor and patch versions (e.g. As a compromise, the last 3 parts of the version number follows Semantic Versioning, leaving the |
Thanks for explanation and for considering. Current versioning is weird and unusual with too many meaningless version numbers. If intention was to just keep IMHO next release should be Can we keep this issue open please, for more discussion? |
You're saying appending a semantic version to After you understand which parts of the current versioning scheme to look at (and which parts to ignore), it's all fine because the only relevant components are the components of semantic version. |
Current repo has deviated from 1.99 quite a bit and 2.0 as originally envisioned will never be achieved so perhaps in the spirit of keeping the legacy idea alive, how about skip straight to 3.0? Not that it really matters because there is not enough contributions to even do releases nowadays but for the sake of keeping things in order, maybe. |
So many numbers are in the release version... Let's consider using standard Semantic Versioning practice please: https://semver.org/
The text was updated successfully, but these errors were encountered: