Feedback is welcome to the Pants 2.17.0 blog post draft. If there are any notable features / changes I've not included, please do comment in the document.

Thanks for starting this! There were a few additional things that were missed from the initial "What's new", which could maybe be added to the post too https://github.com/pantsbuild/pants/pull/19629 (I can take a look later, but I have to do some other work for a bit)

https://pantsbuild.slack.com/archives/C0D7TNJHL/p1692528483580929?thread_ts=1692528451.518099&cid=C0D7TNJHL

The story being the change surfaced an (pants internal) issue with regard to Python interpreter constraints. It’s been since fixed on the 2.18.x line but not yet backported to 2.17. (unless I missed it while being away, updating the PR now..)

okay, amazing, so we will'be able to do

./pants lint --only=visibility ::

in the 2.17, right?

only if merged, yes. cc @happy-kitchen-89482 regarding stabilizing 2.17 we need to make a call if we want to include this or not.

I don't mind doing another RC for this, we can turn it around quickly

It is likely blocked on https://github.com/pantsbuild/pants/pull/19116#issuecomment-1579154246 being picked first.

It looks like #19188 might have a “real” failure? Given it’s a new feature that’s an iteration on a feature from 2.16, I propose that we let it go for 2.17, and ship it/announce it in 2.18 instead. Thanks for the work on attempting to get it in. What do you think?

I’m ok with slipping this one to 2.18 (but I know Alexey would very much like it in 2.17) but if we keep a sane release cadence perhaps 2.18 doesn’t have to be too far out 😃

Yeah, I’m excited for quick releases too!

sure, it can wait till 2.18, not a big deal at all!