8000 Add section on future API standard evolution by rgommers · Pull Request #37 · data-apis/array-api · GitHub
[go: up one dir, main page]
Skip to content

Add section on future API standard evolution #37

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Sep 16, 2020
Merged

Add section on future API standard evolution #37

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70898d7
Add versioning section to "future API standard evolution"
rgommers Sep 13, 2020
300c5ac
Add section on backwards compatibility
rgommers Sep 13, 2020
9744731
Add scope extensions section to "future API standard evolution"
rgommers Sep 13, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Add scope extensions section to "future API standard evolution"
  • Loading branch information
@rgommers
rgommers committed Sep 13, 2020
commit 974473114951fe9f99d6e95f9478d704a622b249
10 changes: 10 additions & 0 deletions spec/future_API_evolution.md
View file
Open in desktop 7BE5
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

## Scope extensions

Proposals for scope extensions in a future version of the API standard will follow
the process documented at:

TODO: link to specific document in https://github.com/data-apis/governance once
it is available.

In summary, proposed new APIs go through several maturity stages, and will only be
accepted in a future version of this API standard once they have reached the "Final"
maturity stage, which means multiple array libraries have compliant implementations
and real-world experience from use of those implementations is available.


## Backwards compatibility
Expand Down
0