4 ms·

React is now React 15 so everybody should expect more easy to upgrade versions moving forward.

• masklinn 11y ago
  I don't know, if they apply semver but just go from major version to major version, that's no change in policy. React 15 -> React 16 makes no BC guarantee.
  • sergiotapia 11y ago
    True true, I am giving them the benefit of the doubt though.
  • pluma 11y ago
    The way the announcement was presented at React.js Conf this year suggests that the version shift also represents a change in stability. Personally I think that from now on React will treat major releases more like Node does -- but of course many people would still consider that pace anxiety-inducing.
• ktRolster 11y ago
  Why? What did they change to make it easier to upgrade? (Obviously adding a 15 to the name doesn't change anything)
  • jsprogrammer 11y ago
    I read the comment as sarcasm.
  • tracker1 11y ago
    If you don't skip versions, you get deprecation warnings for most changes before the breaking change in a subsequent version... jumping 3 versions was the bigger issue, second being that 3 versions in 1.5 years... but that is the JS ecosystem in general right now. Beyond this, tfa is fighting with build tools that are a bit of a mismatch, which is a separate problem... That it only took a day isn't such a big deal really, and surprisingly good... it could have been integrated a couple of times over the course of that 1.5 years, instead of being left to rot.