Skip to content

Add blog post announcing v2022 Array API Standard release #16

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

Merged
merged 11 commits into from
Mar 2, 2023

Conversation

kgryte
Copy link
Contributor

@kgryte kgryte commented Jan 12, 2023

This PR

  • adds a blog post announcing the 2022 revision of the Array API standard.
  • spends some time to covering what has transpired since the initial draft release in Nov 20, as no blog post was published after the final v2021 release.
  • states that the focus for 2023 will be driving adoption among downstream array API consumers.

@kgryte
Copy link
Contributor Author

kgryte commented Jan 30, 2023

As discussed in the 12 January 2022 consortium meeting, I've updated the blog post to announce the release of the test suite and array compatibility layer. I also fixed a few typos and grammatical errors.

This post should be ready for review.

@kgryte
Copy link
Contributor Author

kgryte commented Feb 27, 2023

I've updated this post to note that the array API compat layer now support PyTorch.

@kgryte
Copy link
Contributor Author

kgryte commented Feb 27, 2023

@rgommers Would you mind reviewing?

Copy link
Member

@rgommers rgommers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This read really well. Thanks @kgryte. And apologies for the delay!

@rgommers rgommers merged commit fa7e6de into data-apis:main Mar 2, 2023
@rgommers
Copy link
Member

rgommers commented Mar 2, 2023

@kgryte kgryte deleted the blog-v2022-release branch March 2, 2023 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants