Revisit `cuda-bindings` branching strategy
Offen
Dieses Issue hat noch niemand übernommen.
cuda.bindings
P2
- Vorherrschende Sprache
- Cython
- Sterne
- 3.4k
- Forks
- 329
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 116
Beschreibung
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
- ...
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.