Many applications are depending on this gem in production.
While there is a "1.0 roadmap" at #46 from 2015, I would suggest it is appropriate to do a 1.0 release just off of present 0.4.0 or master branch. So apps using it in production can have some understanding of backwards-compat as related to version numbers going forward. And there is a clear path to do important bugfixes or security patches in a forwards-compat-ensured way.
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.
Perhaps the "1.0 roadmap" could be changed to a "2.0 roadmap".
jrochkind
commented
4 years ago
Many applications are depending on this gem in production.
While there is a "1.0 roadmap" at #46 from 2015, I would suggest it is appropriate to do a 1.0 release just off of present 0.4.0 or master branch. So apps using it in production can have some understanding of backwards-compat as related to version numbers going forward. And there is a clear path to do important bugfixes or security patches in a forwards-compat-ensured way.
semver.org suggests in their FAQ:
Perhaps the "1.0 roadmap" could be changed to a "2.0 roadmap".
Thoughts?