Consider 1.0 versioning
joshtriplett opened this issue · comments
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.
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.