Switch to semantic versioning

[stevewillard]

What are your thoughts on making the next major release 16.0.0? Your changelogs are great, and I can easily pick out the breaking changes, but versioning to go along with that would be nice.

[aahan96]

@stevewillard We are working on improving the Roadmap.md file which will tell the users about the upcoming versions and the path this project is heading towards. Stay tuned. Till then you can follow this update #4205

[nathanmarks]

@stevewillard We are following semver, pre-1.0.0 minor versions are considered breaking (npm respects this too)

[djensen47]

First, I just want to say that this project is great. Thank you!

NPM, Inc. recommends against using pre-1.0.0 semver: https://docs.npmjs.com/getting-started/semantic-versioning

Semver for publishers

If a project is going to be shared with others, it should start at 1.0.0, though some projects on npm don't follow this rule.

If I understand correctly, pre-1.0.0 is what you use before your push to npm. Sure you can do whatever you want but the community is moving away from 0.x.x releases I would hope that this project would be willing to follow the so-called standards of the community as well. Heck, even React itself went from 0.14 to 15.0.

Just my two cents on the subject. 😀