There's quite a few regressions (from onboarding paper-cuts to larger ones) with 2.17 (https://github.com/pantsbuild/pants/milestone/58) and the scie-pants adoption: • https://github.com/pantsbuild/pants/issues/19775 • https://github.com/pantsbuild/pants/issues/19765 • https://github.com/pantsbuild/pants/issues/19751 • https://github.com/pantsbuild/pants/issues/19748 • https://github.com/pantsbuild/pants/issues/19740 • https://github.com/pantsbuild/scie-pants/issues/263 • https://github.com/pantsbuild/scie-pants/issues/267 If this were a commercial project, we'd assign some lucky soul to focusing on triaging them and/or fixing, but we're not and everyone has other reponsibilities... I've looked through them a bit, but definitely won't have time to work on many of them. How can we prioritise and get through the worst of these sooner rather than later? (hopefully getting a 2.17.1 out soon-ish?)

I'm already assigned to 2 of them (3 of them?)

Great! Do you think you'll be able to look at them in the near future? (no pressure, just trying to understand your constraints, e.g. if it's unlikely, maybe they could be unassigned to avoid ambiguity about if someone's working on them... if it's likely, even better!)

https://github.com/pantsbuild/scie-pants/issues/267 is ASAP https://github.com/pantsbuild/pants/issues/19751 is before 2.18 releases, as the feature is experimental and opt-in

as the feature is experimental and opt-in

(Thanks for the reminder. I've explicitly suggested opt-out to the user too.)

It's on my short list, because we want to encourage people to use it. But I'm not worried about quick patch