-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Should we keep using semantic versioning? #319
Comments
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue discusses the applicability of Semantic versioning (SemVer) for Modmail. I personally don’t believe we should use SemVer for our versioning scheme and my arguments are as followed. Feel free to continue this discussion below.
First of all, Modmail is not a public API, nor any API whatsoever, which is the fundamental principle of SemVer. Modmail is considered as an end-user software. This means that Modmail is under no obligation nor have any direct benefits from following SemVer.
The reason behind why developers use semantic versioning is to prevent “dependency hell” for packages that depends on the API (referencing Modmail), but as Modmail is not an API and no packages actually relies on Modmail (they really shouldn’t), this does not apply.
What I believe we should be doing:
According to these respected QA forums, I came up with the following conclusions.
The general census for end-user applications is to make the version user friendly and deploy marketing strategies.
A simple versioning system can still remain as:
However with the following pointers in mind:
Miscellaneous:
Please voice your opinions down below, anything constructive is welcome!
The text was updated successfully, but these errors were encountered: