Your question:
Motivation
The next release of tiledb-feedstock will require us to use vs2022 for its win-64 build. Manually migrating a single feedstock to vs2022 is straightforward and well documented. However, it's my understanding that after we build with vs2022, all downstream conda-forge packages that depend on tiledb will also be required to migrate to vs2022 (and thus their dependencies and beyond throughout the dependency network). Thus I was curious: is their a plan/timeline for migrating the conda-forge win-64 builds to vs2022?
xref: TileDB-Inc/conda-forge-nightly-controller#69, conda-forge/tiledb-feedstock#268
Research
Your question:
Motivation
The next release of tiledb-feedstock will require us to use vs2022 for its win-64 build. Manually migrating a single feedstock to vs2022 is straightforward and well documented. However, it's my understanding that after we build with vs2022, all downstream conda-forge packages that depend on tiledb will also be required to migrate to vs2022 (and thus their dependencies and beyond throughout the dependency network). Thus I was curious: is their a plan/timeline for migrating the conda-forge win-64 builds to vs2022?
xref: TileDB-Inc/conda-forge-nightly-controller#69, conda-forge/tiledb-feedstock#268
Research
Move to vc142 toolchain on windows #1732 - proposed the migration to vs2019. Also noted "The one caveat is that any library built with a given toolset version can only be consumed (e.g. linked) by a toolset version that's the same or newer."
move to vs2019/vc142 conda-forge-pinning-feedstock#3167 - This is the PR that bumped the pin from vs2017 to vs2019
vs2022 for win-arm64 conda-forge-pinning-feedstock#4415 - The PR title says it all
Update maintainer kb windows doc #1956 (comment) - This comment from @h-vetinari nicely summarizes the current practice of conda-forge to be conservative when it comes to updating MSVC