<story><title>New Versioning Scheme for React</title><url>https://facebook.github.io/react/blog/2016/02/19/new-versioning-scheme.html</url></story><parent_chain></parent_chain><comment><author>tolmasky</author><text>This is a great move and hopefully inspires people to take a different look at what versioning is. Right now it serves two masters: marketing and engineering. If everyone just used semver as almost build numbers with meaning, and completely put aside the &amp;#x27;hidden meanings&amp;#x27; of 1.x.y or 2.z.w, we&amp;#x27;d be in a much better place.&lt;p&gt;The main issue with getting hung up on &amp;quot;what is a 1.0&amp;quot; or &amp;quot;when is this 2.0?&amp;quot; is that even if you finally make sense of it for YOURSELF, everyone outside has such a different interpretation that its meaningless no matter what. However, semver for engineering changes has meaning no matter what. Why hurt your users by introducing a breaking API change in the minor category just because &amp;quot;it doesn&amp;#x27;t feel like a major change&amp;quot;?&lt;p&gt;I wish we could just rename version to build, have it be semver and be done with it. Then version can be whatever you want and is completely ignored by computers and engineers. Call it version 1.0, version dog, version whatever &amp;quot;feels&amp;quot; right, while we start moving to a world where we can start maker safer decisions.</text></comment>
<story><title>New Versioning Scheme for React</title><url>https://facebook.github.io/react/blog/2016/02/19/new-versioning-scheme.html</url></story><parent_chain></parent_chain><comment><author>Hovertruck</author><text>Surprised they didn&amp;#x27;t start at 1.0. I understand what they&amp;#x27;re saying with the reasoning, but I don&amp;#x27;t think I agree with it.&lt;p&gt;Not that it really matters, I guess.</text></comment>