Revisit `cuda-bindings` branching strategy
Open
Nobody has claimed this yet.
cuda.bindings
P2
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
Right now we have cuda-bindings 12.9.x maintained in the 12.9.x branch. This causes frictions for
- understanding the maintenance scope
- it is not obvious at all that only
.github/,ci/,cuda_bindings/, andcuda_python/are maintained there
- it is not obvious at all that only
- tracking and backpoting fixes (https://github.com/NVIDIA/cuda-python/issues/965)
- maintaining CI infra (https://github.com/NVIDIA/cuda-python/issues/1058) and docs (https://github.com/NVIDIA/cuda-python/issues/809)
- releasing 12.x packages (https://github.com/NVIDIA/cuda-python/issues/1120)
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/andcuda_bindings_13/on themainbranch - Generate the same binding code that have a bunch of macros that can be toggled at build time to target CUDA 12/13
- ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.