Skip to content

Revisit cuda-bindings branching strategy #1199

@leofang

Description

@leofang

Right now we have cuda-bindings 12.9.x maintained in the 12.9.x branch. This causes frictions for

We would like to lower the burden and the mental overhead on the team. Possible solutions include:

  • Eliminate the backport needs by hosting two directories cuda_bindings_12/ and cuda_bindings_13/ on the main branch
  • Generate the same binding code that have a bunch of macros that can be toggled at build time to target CUDA 12/13
  • ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    cuda.bindingsEverything related to the cuda.bindings moduletriageNeeds the team's attention

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions