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

Tag a 1.0.0 #283

Closed
davidanthoff opened this issue May 19, 2019 · 1 comment · Fixed by #287
Closed

Tag a 1.0.0 #283

davidanthoff opened this issue May 19, 2019 · 1 comment · Fixed by #287

Comments

@davidanthoff
Copy link
Collaborator

Could we tag a version 1.0.0?

That would make it much easier for packages that depend on this one here to use semver compat bounds in Project.toml. The problem is that pre 1.0.0, every minor update is considered breaking, whereas starting with 1.0.0 one can use the full semver semantics, which make everything easier.

Also, it seems that this package is so widely used with the current API, that one might as well declare what we have as stable and done, right?

@TotalVerb
Copy link
Collaborator

I think this is reasonable. Let's get all the current outstanding PRs dealt with first, and then tag a first major version.

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

Successfully merging a pull request may close this issue.

2 participants