Skip to content

Instantly share code, notes, and snippets.

@iamdustan

iamdustan/react-and-the-train-schedule.md

Created May 18, 2016 19:17
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save iamdustan/2df7a749e1c8d741174fa1a25eccc11d to your computer and use it in GitHub Desktop.
Save iamdustan/2df7a749e1c8d741174fa1a25eccc11d to your computer and use it in GitHub Desktop.
Download ZIP
Raw
react-and-the-train-schedule.md

React and the Train Schedule

Some random thoughts about the possibility of React joining the train schedule:

Benefits

  • More frequent releases
  • Releases become a normal thing in the React community
  • Bug fixes and patches make it out faster
  • Facebook is no longer solely responsibly for stability; community can take a more active involvement

Cons

  • Regressions make it out faster, new features have less time to bake.
  • Consumers need to take on a bit more burden to stay current.
  • Pain during transition while community evolves semver/package.json model
  • An explosion of React versions for community modules to support

Questions

  • What will the official maintenance/support matrix be? Historically, it’s only been latest. With a plethora of releases will it need to expand?
@zpao
Copy link

zpao commented May 18, 2016

I think the official matrix might actually pretty similar to what we've done for 3 years. There's a latest stable release and that's it. It is whatever the latest version of 15 is. We never backported bug fixes that landed in 0.14.1 back to 0.13.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment