Paul Moore answered on discord to recommend us to use our own PEP 503 index (instead of test.pypi.org) to publish nightly builds. I think setting up a new shared organization on https://anaconda.org/ to shared the wheels of nightly builds for cython, numpy, scipy, pandas, scikit-learn, gensim,... would be the best way to go forward. It makes it possible to preserve the convenience of the shared nightly builds currently uploaded to http://wheels.scipy.org . anaconda.org does not have a built-in retention policy but the anaconda-client package provides a command line "anaconda remove" to delete individual files. So it should be possible to write a CRON job somewhere to clean-up old nightly builds (which is currently not possible to do on test.pypi.org). I have also investigated further if we could do the same on Azure Artifacts but it is more cumbersome: to share upload credentials to a shared feed to several projects' maintainer teams requires generating "Personal Access Tokens". Each token has a maximum validity limit of 1 year. We would have to reconfigure all the CIs at least once a year which is a bummer. For the name of the shared anaconda cloud organization, would "scipy-nightly" be fine? Or maybe "scipy-wheels-nightly" to be extra explicit? The intent would be to share this space with the aforementioned projects of the scipy ecosystem. For the second use case of a staging wheelhouse for (tagged) release automation, one could use test.scipy.org as it matches the intended use case of that service. -- Olivier