We've got 4 post-2.10.0 cherry-picks queued. I'm r...
# development
e
We've got 4 post-2.10.0 cherry-picks queued. I'm releaser this week and will be sending up a 2.10.1rc0 but wanted to check in for any strong opinions about when this is done. My preference is ~nowish since at least 1 pick directly addresses a user-reported issue where they are using 2.10.0.
h
Yes, I agree that 2.9, 2.10, and 2.11 are all probably ready for release candidate. 2.11 will need more bug fixes, but I don't think there is anything currently queued where we need to wait Let me know if you would like to split any of that up
e
2.9.2rc0 I think can wait until Friday. It's just 2.10.1rc0 I'm interested in moving up sooner.
I may just do 2.10.1rc0 today and leave 2.9.x and 2.11.x for Friday. 2.11.x at least definitely has queued work.
w
i’ve got one more bound for 2.10.x today: https://github.com/pantsbuild/pants/pull/15031
👍 1
e
Sounds good - I'll hold off until this evening after that.
w
thank you sir.
more generally, i’ve been pushing on using the milestones for 2.10.x and 2.11.x more heavily, and they can help keep track of these. although they’re more of a conversation starter than an answer to the question, since it’s not clear how many of the tagged tickets are aspirational vs blockers.
e
Yeah, that may be a good idea, but I think I'd always drop in and ask anyhow until the day we have a bot ripping a release from a milestone.
🤞 2
w
took longer than i was expecting, sorry: https://github.com/pantsbuild/pants/pull/15033 … if i missed the boat, would be happy to do some releases on Friday.
ok, all of my stuff is in. i’ll revisit on Friday and do releases if needed.
e
Ok. I'll get 2.10.x rolling then.
🙏 2