-
Notifications
You must be signed in to change notification settings - Fork 0
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
Please make a release #1
Comments
I think releases would be good, but I'm not sure about semantic versioning for this project (yet). Semantic versioning mandates various levels of compatibility between various levels of releases. I think, sadly, that our software development methodology as a group is not rigorous enough to make those compatibility guarantees from release to release. I would be more in favor of a date-based release (e.g. |
I think you are assuming too much of sentimental value to the use of a version number. In the end, people don't really care that much. Semantic version numbers are easier to pronounce and to read compared to dates. If the software is alpha alpha for now and the foreseeable future I would recommend to starting numbering at 0.0.1 and move up from there. I don't see how this low number semantic versioning naming scheme would give a false impression of stability. That said, having a release is better than no release, so if you guys prefer to use a date-based release anyway I'm not against. |
A good hybrid would be to start with |
The summary section on https://sermver.org says:
It's a great model, but I don't think we have enough testing infrastructure or code review time to go through and classify whether each change is a PATCH, MINOR, or MAJOR change. Without that, I think mimicking a semantic version numbering scheme is misleading to those who expect the above semantics and confusing/overly complicated for those that don't know about semantic versioning. |
I think using |
Ok so what do we do? :) My worry is that when we make and distribute the packages they are updated and upgraded properly when new versions are made. When semantic versioning (or the data based hybrid) is used, the upgrade path works properly. But if in the future you switch from a pure date as a version to a semantic version at some point this will break: |
for example 0.1
Please don't name it 0.1alpha, rather use semantic versioning https://semver.org/
The text was updated successfully, but these errors were encountered: