Open
Description
Tasks for cuda-core and cuda-bindings patch release
- File an internal nvbug to communicate test plan & release schedule with QA
- Ensure all pending PRs are reviewed, tested, and merged
- Check (or update if needed) the dependency requirements
- Bump the version
- Create a public rc tag
- Point QA to fetch public artifacts (wheels) from the GHA run ID, example:
gh run download 12323257563 -p "cuda-core*" -R NVIDIA/cuda-python
- Wait for QA reports and fix any issues found
- Finalize the doc update, including release notes ("Note: Touching docstrings/type annotations in code is OK during code freeze, apply your best judgement!")
- Update the docs for the new version
- Create a public release tag
- If any code change happens, rebuild the wheels from the new tag
- Update the conda recipe & release conda packages
- Upload conda packages to nvidia channel
- Upload wheels to PyPI
- Post-release QA
- Finalize the announcement update
- Send out the announcement internally
- Send out the announcement externally (GitHub Release -> Announcement)