<h2 dir="auto">The versioning scheme is actually quite childish and doesnt comply with any industry standard.</h2>
<p dir="auto">major.minor.patch</p>
<p dir="auto">major - this will break previous libraries that use this</p>
<p dir="auto">minor - this adds new functionality/features</p>
<p dir="auto">patch - something is broken</p>
<p dir="auto">0 indicates that its still in development and anything can change at any time. Yet people are already using your product in production and relying heavily on it.  You send a message to your end users that you do not care about them or their compatibility issues by not using semantic versioning.</p>
<p dir="auto">NodeJs finally moved to real semantic versioning with IOJS merged in they are now up to 4.1.2 and clearly explains the backward compatability issues with the different versioning.</p>
<p dir="auto">Almost every release introduces breaking changes. It would be easier to maintain if React bumped the first digit of the version every time there was a breaking change.</p>