JRG: This ended up in a conversation about pip interoperability (missing in our PR so far) with points that we should cover in another meeting, having Filipe Lains (Quansight) attend.
[CJW] Deprecation of old conda versions, ~= and = matchspec not supported by older conda versions. Having repodata entries with these cause old conda to be unable to update envs.
To some extent conda-forge can do this by itself via repodata patches, but community consensus would be much better
SA: hmmm, reconciliation repodata with a matching specification version for the current environment, with that data being sufficient for conda update (then you're hosting small additional amounts of repodata per spec version). probably has to be paired with minimal override conda settings?
JRG: It would work like conda update -c recovery conda or similar.
All: deprecation cycle for conda?!
JL: And in general, better communication towards the community. CLI notices?