5 ms·
0.13 -> 1.0 was breaking 1.0 -> 2.0 was fully BC That was 2 years with only one breaking change. 2.0 -> 3.0 removed deprecated 1.0 API, fully BC with 2.0 The
by ryanflorence 10y ago
0.13 -> 1.0 was breaking
1.0 -> 2.0 was fully BC
That was 2 years with only one breaking change.
2.0 -> 3.0 removed deprecated 1.0 API, fully BC with 2.0
The only churn is for people who don't stick to stable releases, and that's their own problem.
- colept 10y agov2.0.0 released this on Feb 10, 2016 v3.0.0-alpha.1 released this on May 19, 2016 v3.0.0-alpha.3 released this on Aug 2, 201 v3.0.0-beta.1 released this on Sep 16, 2016 v4.0.0-0 released this on Sep 13, 2016 v3.0.0 released this on Oct 24, 2016 > ... and that's their own problem. Hence deprecation right out the gate. V4 is much better, great work - but blaming users for API churn does not make me confident. Sure users could have used a stable release, but then upgrade twice? What confidence is there that it won't churn again?
- ryanflorence 10y agoI'm so confused. There are only two actual releases there: v2.0.0 and then 8 months later v3, where all that happened was v1 API was removed. If you only keep up with the stable releases your life has been simple with React Router.
- ryanflorence 10y agoAlso, don't upgrade. v3 is going to maintained with bugfixes and whatever needs to happen to be compatible with new React releases indefinitely.