he/him 
Add new API with warnings for old API in ___, drop old API in ___.
-
@jo_liss yeah, I also think it should be 2.0, then 2.1 drop backwards compat, but the poll shows you and I are alone so far.
@ryanflorence @jo_liss that breaks semver. breaking changes need to be made in a major version.
-
-
- 1 more reply
New conversation -
-
-
@sebmck@ryanflorence@jo_liss the question is whether deprecation is a breaking change. Some say yes because of warnings. - 11 more replies
New conversation -
-
-
@sebmck@ryanflorence In practice, if warning in 2.0 says "x is deprecated & will be removed in 2.1", does the removal cause any problems? -
@jo_liss@sebmck@ryanflorence major version bump should happen on removal. Anything I can use in 2.0 should work in 2.1..as I understand it
End of conversation
New conversation -
-
-
@sebmck@ryanflorence@jo_liss semver assumes all breaking changes are knowable, which isn’t a safe assumption nor reflective of reality. -
@sebmck@ryanflorence@jo_liss the versioning scheme of react < 1.0 and what@ryanflorence are proposing is much more sensible, IMO
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.