RFC: Align conda releases between `conda-forge` and `nvidia` channels

[leofang]

While currently the cuda-python conda packages on both channels:

• https://anaconda.org/conda-forge/cuda-python (from https://github.com/conda-forge/cuda-python-feedstock)
• https://anaconda.org/nvidia/cuda-python

are maintained by the same team, they are built using different conda recipes (the nvidia channel one is internal). In particular, the cuda-version meta package is not honored by the nvidia varaiant, which starting CUDA 12.5 is considered an outdated practice.

This RFC is a record for our intention to make sure the cuda-python package (and all future packages that we build, #105) in sync and interoperable between both channels.

[jakirkham]

Happy to chat with Vlad and yourself on alignment 🙂

[vzhurba01]

After comparing the two recipes, the nvidia channel recipe doesn't have any changes that need to be ported to the conda-forge-feedstock. Therefore the plan going forward is that we will first go through the steps to make a conda-forge release, and then distribute those same packages to the nvidia channel. Note that the previous nvidia channel packages already had a dependency on conda-forge, so there should be no noticeable effects.

The internal nvidia recipe is free to be archived and is now being marked as such. Closing.

[jakirkham]

Thanks Vlad! 🙏

If any questions come up during this process, please feel free to reach out 🙂