Change SPEC4 to cover using and building nightly wheels #195
Conversation
This describes the process for adding people to the anaconda organisation that hosts the wheels.
|
An idea that @Carreau brought up that I think is great but should be for a version two, not now: setup a small proxy (e.g. cloudflare worker, small python script?) that aggregates several simple PyPI indexes (not sure if this is the right jargon). That way each project could publish their nightlies where ever they want and it would show up in the aggregate. It would make managing credentials and such simpler. The level of indirection would also allow for phasing out/in new locations, etc. The reason to not do it as part of this round is that building the service and running it is some amount of work, especially in six months time when the initial excitement has passed. |
6e56515 to
c36eac0
Compare
c36eac0 to
ddf9d22
Compare
|
I'd propose we merge this so we can start using it, linking to it, etc. This would also allow projects to list themselves as "projects which adopted this approach" |
|
OK, let's merge. |
🚧 This is work in progress.
The goal is to create a SPEC that covers both using and creating nightlies.
I am trying to keep it kind of high-level, giving examples of how to do the things that are new (e.g. uploading to the nightly area) but not be too prescriptive/show full blown CI setups because I assume the target audience are likely to already have fairly sophisticated/complex/complicated CI setups. For example scikit-learn uses Azure to run their unit tests, but uses GH Actions to build wheels. I think this is good, we don't want people to revamp their whole CI setup.
Closes #188