New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.0 #727
Conversation
|
|
|
|
| remove, only add_ strategy. | ||
| [#46](https://github.com/json-api/json-api/issues/46) | ||
| Now that JSON API has reached a stable version 1.0, it will always be | ||
| backwards compatible using a _never remove, only add_ strategy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the point of a major version number with this strategy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm interpreting this as "we're going to follow semver, and we don't ever plan on making a version 2.0."
|
Outstanding! What a huge accomplishment for the community. Big thanks to the core team and everyone that contributed. |
|
|
|
|
de30b5f
to
2d89607
Compare
|
|
|
Woohoo! |
|
YAY!! |
|
|
|
Best Friday commit EVER! |
|
|
|
MUCH EXCITE! |
|
|
|
Great job everybody! |
|
|
|
YAYAY! |
|
|
|
|
|
|
|
|
|
Congratulations, and big thanks to the editors for driving this! |
|
|
|
Thank you! |
|
Well done |
|
Super awesome to have a 1.0 spec. Already putting into use thanks so much! |
|
|
|
Awesome |
|
|
After two years, four release candidates, hundreds of contributions, and untold hours of discussions, we're finally ready to declare the JSON API specification stable!
JSON API v1.0 marks the beginning of a new phase in the life of this specification. From this point forward, the base specification will remain backwards compatible and will only change additively.
Thanks so much to this wonderful community for discussing, contributing to, and implementing this specification over this long journey. @wycats, @steveklabnik, @tkellen and I could not have done this without your help!