-
Notifications
You must be signed in to change notification settings - Fork 236
Closed
Labels
P1Medium priority - Should doMedium priority - Should dosupportAll things related to the project that can't be categorizedAll things related to the project that can't be categorizedtriageNeeds the team's attentionNeeds the team's attention
Milestone
Description
Release managers need to go through this check list and ensure all tasks are done
- Is this release for
cuda-bindings/cuda-python?- Push any internal updates for accommodating a new CTK release to the public (IMPORTANT: Need to wait for CTK posting!)
- Bump the version
- Follow the check list for
cuda-corebelow for the remaining steps
- Is this release for
cuda-core?- File an internal nvbug to communicate test plan & release schedule with QA
- Ensure all pending PRs are reviewed, tested, and merged
- 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
- Update the docs for the new version
- Create a public release tag
- If any code change happens, rebuild the wheels from the new tag
- Upload wheels to PyPI
- Finalize the announcement update
- Send out the announcement
- Internally
- Externally (GitHub Release -> Announcement)
- Update the conda recipe & release conda packages
- Post-release QA
Metadata
Metadata
Assignees
Labels
P1Medium priority - Should doMedium priority - Should dosupportAll things related to the project that can't be categorizedAll things related to the project that can't be categorizedtriageNeeds the team's attentionNeeds the team's attention
Type
Projects
Status
Todo