-
Notifications
You must be signed in to change notification settings - Fork 157
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
[Feature Request] use semantic versioning #266
Comments
Hey @justmiles Thats why i settled on releases based on the date 2024-05-05.1, would be the first release for today, as an example. This doesnt force anything on contributors. Also the people who want to auto-update or version-pin got involved so i create the following. Branches:
This enables pinning to a commit and also enables people who want to use Watchtower. I know theese are 2 entire topic, but in the end for automation they inter-twine with each other to give the user/admins/players the best experience. How would you suggest to change all of that? |
Using a date-based versioning system is indeed a valid approach. While it may have a few shortcomings, considering the size of the project and the number of maintainers/contributors, you may find it to be the most practical approach. If you choose to continue using the date-based versioning strategy, the only adjustment I would encourage is to tag the source commit ( If you are open to reconsidering semantic versioning, let me address some of the concerns you raised.
Regarding tools like Watchtower for automatic updates: I too automate my updates - I use Renovate, which effectively solves the same problem. Minor and patch releases are automatically updated, but most users prefer to avoid automatic installations of breaking changes. When a major release is available users are notified by their automation tool and can decide whether to approve the automatic deployment or perform a manual upgrade. This delineation between regular and breaking changes isn't captured with a date-based releasing strategy - discouraging automatic updates. Again, a date-based approach is certainly valid. I'll personally still auto-update with the date-based tags and just fix-forward should any breaking changes get introduced. Hope this helps! |
@justmiles Thanks for the long and somewhat complicated text 😄 |
Yeah for sure 😊 |
@justmiles feel free to join Discord and DM me - Whenever you feel like it and have time |
Which discord server - do you have a link? |
Have you read the Important information text above
Describe the feature
Hi @jammsen - this docker image along with several others have proved to be a reliable source for ready-to-go servers. However, it's difficult to keep the container itself update without versioning.
Would you consider embracing semantic versioning for this repo?
https://semver.org
Additional information
Final checks
The text was updated successfully, but these errors were encountered: