v2.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?
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?