Skip to content
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

Time for version 1 (follow semver)? #520

Open
razor-x opened this issue Jul 24, 2022 · 0 comments
Open

Time for version 1 (follow semver)? #520

razor-x opened this issue Jul 24, 2022 · 0 comments

Comments

@razor-x
Copy link

razor-x commented Jul 24, 2022

Anything blocking 1.0.0 for this project? Seems it is widely used in production at the point.

I'd like to quote the argument directly from this post on a different project (graphql/graphql-js#1005):

I think it's time to move to 1.0+ versioning so that we can actually use the version number to transmit meaningful semantic information (ie. that a "major" version bump is a compatibility-breaking change). Our current version numbers (of the form v0.x.y) transmit basically nothing, because:

Major version zero (0.y.z) is for initial development. Anything may change at any time.

This entry from the Semver FAQ is also helpful:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

I think all of those apply to this package, so let's do it with the next release.

See also https://0ver.org/

Best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant