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
- ...
Right now we have
cuda-bindings12.9.x maintained in the12.9.xbranch. This causes frictions for.github/,ci/,cuda_bindings/, andcuda_python/are maintained there./ci/tools/download-wheelsdoes not exist in the backport branch #1120)We would like to lower the burden and the mental overhead on the team. Possible solutions include:
cuda_bindings_12/andcuda_bindings_13/on themainbranch