Skip to content
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

Release pre-release 2.3.0rc20240410. #605

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Conversation

stellaraccident
Copy link
Contributor

Includes some scripting and release documentation updates that have been in my queue for a while.

In this version, we start executing on the change to deploy the iree-turbine package and the iree.turbine namespace. This is just a copy of the shark-turbine package currently and the top level namespace is just a redirect of the public API. The next release will complete the switchover.

Since this is pushed as an rc, it is a pre-release requiring installation with the --pre flag. When torch 2.3.0 drops, we should push a final.

Includes some scripting and release documentation updates that have been in my queue for a while.

In this version, we start executing on the change to deploy the `iree-turbine` package and the `iree.turbine` namespace. This is just a copy of the shark-turbine package currently and the top level namespace is just a redirect of the public API. The next release will complete the switchover.

Since this is pushed as an rc, it is a pre-release requiring installation with the `--pre` flag. When torch 2.3.0 drops, we should push a final.
@stellaraccident stellaraccident merged commit e158bae into main Apr 11, 2024
4 checks passed
@stellaraccident stellaraccident deleted the prepare_release_2.3.0 branch April 11, 2024 00:37
ScottTodd added a commit to iree-org/iree-turbine that referenced this pull request Nov 6, 2024
The `docs/releasing.md` file was first introduced next to the
`build_release.py` script in
nod-ai/SHARK-ModelDev#605. I don't see that file
in this repository (iree-org/iree-turbine) though, despite
nod-ai/SHARK-ModelDev#655 claiming that it had
been upstreamed. Since the packages involved have changed over the
months (shark-turbine --> iree-turbine naming, see also
#28), I also updated the
document to reflect the current setup.

The `iree-requirements.txt` file was being used to pin versions of the
`iree-compiler` and `iree-runtime` that would be released together with
this `iree-turbine` package. That was overlooked when
#115 removed pins from that
file. I've reworked the script to reference `iree-requirements-ci.txt`
for now, but we can continue to iterate on the cross-project release
process going forward (with docs this time).

I've updated the version in code from 2.3.0 to 2.5.0. We can push a
release to https://github.com/iree-org/iree-turbine/releases and
https://pypi.org/project/iree-turbine/#history using the new version
next. Note that 2.3.1, 2.4.0, and 2.4.1 were released to PyPI without
updating the code or GitHub releases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant