Repository navigation
Align Dask nightly versioning scheme with versioneer #369
Description
Currently, the Dask conda nightlies' versions do not match up with the version returned by versioneer:
→ conda list dask-core
# packages in environment at /raid/charlesb/miniforge3/envs/test-dask:
#
# Name Version Build Channel
dask-core 2024.3.1a240315 py_gf9310c440_3 dask/label/dev
→ python -c "import dask; print(dask.__version__)"
2024.3.0+3.gf9310c440
Conda has support for these version strings, so in theory it shouldn't be too difficult to modify the recipes across the Dask repos publishing nightlies to use them instead.
Tracking this here since it may potentially require a few PRs across multiple repos to complete; ideally would like to look into this after dask/distributed#8574 is addressed.
Activity
[-]Update version scheme for Dask nightlies[/-][+]Align Dask nightly versioning scheme with versioneer[/+]jakirkham commentedon Mar 20, 2024
This is probably achievable by bumping the patch version after each release
If this were done, the Conda recipe logic could be unwound (as this would already be handled for us)
charlesbluca commentedon Mar 21, 2024
By this, do you mean doing something similar to RAPIDS and creating an "alpha" tag (i.e.
2024.3.2a)?