conda-forge / conda-forge/pytorch-cpu-feedstock
v1/rattler-build adoption and anaconda/conda-forge alignment strategy in general.
- Dominant language
- Shell
- Stars
- 32
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
A summary of Anaconda's current state with regards to rattler-build/v1 format adoption is [here](https://hackmd.io/@conda-forge/HyypoJnLyl).
The v0/v1 formats aren't miles apart but we already have to do some work to adapt recipes to anaconda's main distribution, this would increase the amount of that work. However, we don't want to block or stymie community efforts. In the end, it should be judged as to whether it's a net benefit here (conda-forge) to wait or go forward, I think. Hopefully aligning efforts is a net benefit to conda-forge, too.
We could also here discuss wider strategies on collaboration given the different working approaches.
Contributor guide
Assessment
This issue has not been assessed yet.