-
Notifications
You must be signed in to change notification settings - Fork 47
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
Is cn-infra using semver? #285
Comments
Bumping this. /cc @ondrej-fabry @jmedved @edwarnicke |
@fkautz isn't this a bug report requesting SemVer? ;) Sure, we could follow strict SemVer just expect having major version increased quite regularly. |
If you're not ready for a 1.0.0 release, semver allows for 0.x releases to
be bumped up without worrying about backward compatibility until you are
ready to release a 1.0.0.
…--
Frederick F. Kautz IV
On Tue, Aug 14, 2018 at 1:53 PM, Ondrej Fabry ***@***.***> wrote:
@fkautz <https://github.com/fkautz> isn't this a bug report requesting
semver? ;)
Sure, we could follow strict semverm just expect having major version
increased quite regularly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#285 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAISGscJV1m9AY_Q4myL90XDNmSlfdh_ks5uQzi_gaJpZM4UZbeA>
.
|
Seems too late for that. 😟 This project seems to start with 1.0 when it was open-sourced on GitHub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If so, can this be documented? This would help developers do the right thing with their dependencies. If not, I'll open a new bug report requesting semver be used ;)
The text was updated successfully, but these errors were encountered: