https://pantsbuild.org/ logo
Join Slack
Powered by
<@U6ZRNH0TC> for 1.16.x, everything I wanted is no...
# announce
h
@aloof-angle-91616 for 1.16.x, everything I wanted is now included. Once we fix PEX release, would be great for this to be the last dev release so that next week we can start 1.16.0rc0 and then 1.17.0.dev0
a
agreed, when the osx wheel building is done we can get a move on, sorry for the wait
🔥 1
w
there is one other potential thing that we might want to discuss blocking cutting 
1.16.x
on, but it's a UK holiday, so Daniel and Borja are both not able to speak to it today
a
i think there's enough work to do to validate the release branch before cutting it that we can wait until tuesday
w
basically, i'd really like to get "fork removal" into 
1.16.x
... they may or may not agree on delaying cutting until then, and i'm not 100% sure how close the branch is. but basically, on tuesday we should have a go/no-go on waiting
đź‘Ť 2
h
Don’t we have to do one more dev before we do RC in order to include all the recent changes?
w
there isn't really any firm correspondence between the number of dev releases and stable releases (or the timing)
h
No I mean that isn’t RC0 not supposed to have many changes in it? We have 10+ PRs right now that haven’t been released. Can those be included in RC0, or have to first go through a dev release?
a
https://www.pantsbuild.org/release_strategy.html i always understood it as "dev releases are done on a timer, rcs are done whenever the branch is good to go"
the notes changes required to cut the branch will include fixes since the last dev release
w
@hundreds-father-404: no, rc0s are effectively just dev releases
h
Ohh okay, that’s where I was confused. Thanks!
a
please keep asking questions like that the answer isn't always obvious
❤️ 1
w
ok, so until we discuss that on tuesday, i've created https://github.com/pantsbuild/pants/milestone/24 and put that in it cc @salmon-summer-38098
đź‘Ť 1
a
thank you!
i've just added https://github.com/pantsbuild/pants/pull/7591 to the 1.16.x milestone too
đź‘Ť 2
l
So no release from me this weekend, looks like?
w
@limited-country-20626: a dev release would be appreciated
đź‘Ś 1
l
ah, I thought I was seeing that was broken
w
if 
1.16.x
gets cut, it definitely won't be before tuesday
l
kk, will do.
w
...oh, hah. yes. it is broken.
l
ah
w
whoops. sorry.
l
I am looking into my patches last year though
I think I hit this same resolve issue internally
when I introduced multiple interpreter paths
e
@limited-country-20626 since I am working the release fix here presently I'd be happy to take on the dev release later tonight if you want to swap.
l
sure, I would be happy to. Thank you for tackling the error!
❤️ 1
just slot me in for your next
e
Excellent. I'll update the calendar entries.
l
🙏
a
I would be in favour of cutting 1.16.x ASAP because there are a bunch of useful fixes in there, but that plays into my bias of “I’d rather cut two releases close together, than delay one release until a feature is done”
đź’Ż 1
h
I agree. As we see in your post in #python3, having to support python 2 is an unnecessary burden and the sooner we can drop that, the better.
Open in Slack
PreviousNext
Powered by