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.

Sign up for GitHub

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

Jump to bottom

Consider 1.0 versioning #57

Open
joshtriplett opened this issue Oct 9, 2019 · 1 comment
Open

Consider 1.0 versioning #57

joshtriplett opened this issue Oct 9, 2019 · 1 comment

Comments

@joshtriplett
Copy link
Collaborator

I think ansi_term seems ready to use 1.0 versioning, and that would also help people consolidate on the same version. Currently, I see multiple versions in the same dependency trees, because semver doesn't consider 0.x.0 and 0.y.0 compatible. Moving to 1.0 versioning would allow semver-compatible upgrades from 1.x.0 to 1.y.0.
@rneswold
Copy link

rneswold commented Nov 8, 2021

There hasn't been a tag since before this issue. Sounds pretty stable!

I agree that the 0.x versioning in cargo is annoying. Please consider a 1.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshtriplett @rneswold