CUDA 12 version in cbc.yaml - plans? about conda-forge-pinning-feedstock HOT 4 OPEN

The usual process when making updates to the global pinnings is

1. Add a migrator
2. Update feedstocks with the migrator via the bot (potentially with some manual intervention)
3. Close out the migrator (once it is sufficiently complete, which can be somewhat subjective)

After 3, the global pinnings are updated

More information in these docs

Currently there is a CUDA 12 conda-forge migration running, which is being handled with this migrator. Also here is the current status of the CUDA 12 migrator. It is ~68% complete at the time of this writing

As the CUDA 12 migration has involved more changes than the average migration, there is a detailed write up of the changes involved and the reasons for them in issue ( conda-forge/conda-forge.github.io#1963 ). This provides more guidance on how feedstocks can build with CUDA 12 packages

from conda-forge-pinning-feedstock.

Thanks to @h-vetinari recent comment ( conda-forge/conda-forge.github.io#1963 (comment) ) was looking again at the CUDA 12 migrator status. Here are some observations:

• 95% are either migrated or already have a migration PR
  • 75% have CUDA 12 packages
  • 20% have an open PR
• 5% have not gotten a PR
  • 3% are waiting for parents to be rebuilt
  • 2% the bot errored trying to make a PR

Based on this, would agree the migration has reached its natural conclusion

Given this would recommend we close out the migration. Have added this in PR: #5613

Also to make sure that newly added packages build with CUDA 12 successfully (given the new package structure), have submitted PR: conda-forge/staged-recipes#25675

from conda-forge-pinning-feedstock.

cc @conda-forge/core

from conda-forge-pinning-feedstock.

I agree. Let’s close it

from conda-forge-pinning-feedstock.