Skip to content

[TEST] #344

Closed as not planned
Closed as not planned
[TEST]#344
@leofang

Description

@leofang

Tasks for cuda-bindings / cuda-python release

  • Push any internal updates for accommodating a new CTK release to the public (IMPORTANT: Need to wait for CTK posting!)
  • Follow the check list for cuda-core below for the remaining steps

Tasks for cuda-core release

  • File an internal nvbug to communicate test plan & release schedule with QA
  • Ensure all pending PRs are reviewed, tested, and merged
  • Update the dependency requirements, if needed
  • 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
  • Send out the announcement externally (GitHub Release -> Announcement)
  • Update the conda recipe & release conda packages
  • Post-release QA

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageNeeds the team's attention

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions