Will be releasing 2.3.0.dev1 today (a couple days ...
# announce
h
Will be releasing 2.3.0.dev1 today (a couple days late)
h
@hundreds-father-404 are we also going to do a dev release tomorrow? I'd like to get https://github.com/pantsbuild/pants/pull/11484 in once it's ready, which will hopefully be soon
h
I'm not sure who's on the release calendar, I got locked out of it for some reason. But I imagine no, we wouldn't How close do you think you are to landing it? I can wait a little longer, but it's bad I waited till today to do the release. With getting your change in, reminder that users (like Toolchain) can consume from a built SHA
h
should have an update to that PR ready in the next few minutes, but yeah toolchain can always build from a SHA I suppose
h
I'm release human tomorrow
Sounds like no point in doing a release until some time next week though
@hundreds-father-404 Let me see what happened with the release cal
h
@happy-kitchen-89482 I suspect I won't be able to release 2.0.2rc0 as planned because of my M1 and Python 3.9. Unclear, I haven't assessed the damage yet
Actually Benjy, can you please finish 2.3.0.dev1 and 2.0.2rc0? I'm happy to send the release emails and update docs I only cannot physically run
release.sh
without making code changes, and we agreed I should put all Py39 on pause for now
h
Sure, tell me what actions you want me to run, just run the release script in your branch?
h
Run it on master branch, ensuring that you're on the release prep commit that's been merged Also run it on 2.0.x from the pantsbuild repo, using the latest commit
I can handle everything other than running the script
h
Running now
❤️ 1
Ooops, dropped the ball. 2.3.0.dev1 release script ran successfully.
Running in 2.0.x now
To be sure, you want me to run it at commit 0c4ea52ce658f5b6d806ea69e43df3b8766412c1 ?
h
Thanks! Yes please
h
Done
h
Thank you! Announced