CC @broad-processor-92400 this was discussed in the meetup (not this proposal specifically. It didn't exist yet 😛) This is the outcome of the discussion, which was generally favorable.

Also CC @gorgeous-winter-99296 please let me know your thoughts from your unique perspective as our most prolific open-source external plugin author 🙂 (Speficially the bits on plugin support)

Would anyone object to me uploading the relevant wheels to prior releases (where available from PyPI)? I think it'd be nice to simplify where the wheels are coming from if someone is supporting multiple Pants versions. (Like Tom 🙂) We can cap it at 2.14.x or something

It has begun

I love downloading from AWS S3 with a PyPI facade and uploading to AWS S3 with a GitHub facade, all through my computer! 😂

2.117 RCs, all of 2.16 stable and RCs have wheels uploaded. Slowly working through 2.15 now 🙂

I have decided to make Microsoft run this for me and am running it in GitHub actions

Ok it turns out that: • Having Microsoft run the jobs (they run in their VPC right? So faster upload bandwidth?) • Running like 15 at a time Makes this go quicker! The last few wheels are being uploaded now. Then the plan is to download dev releases from S3, reversion, then upload. Then every single release should have wheels uploading, going back to some versions of v1

OK, every non-dev release should have wheels uploaded that are on PyPI. I think that some releases don't have wheels on PyPI (like this, which on PyPI is this). I suspect they were pulled for space constraints. So, next up is to populate the dev releases by reversioning the binaries.pantsbuild.com git-versioned wheels. Exciting stuff!

re-versioned dev releases are starting... https://github.com/pantsbuild/pants/releases/tag/release_2.18.0.dev5

Most of them are done for v2

OK, and lastly, going to upload reversioned wheels for all the non-dev, non-stable releases (these were yanked form PyPI due to size constraints). Hopefully by EoD we'll have backpopulated everything for v2 (and likely v1)