2.16 has been delayed for quite a while at this point: it’s had 7 dev releases, although in wall clock time, it’s been in development since ~Nov 1st (not terribly surprising with the holiday, but!) i think that we should consider bumping the experimental shell command stabilization to 2.17, and cutting 2.16.x this week.

If we don’t land the stabilisation this week, then fine. There’s a couple of tickets that should probably land short of renaming the targets that should be quick to implement, though

(or splitting what we stabilize, but that’s probably trickier)

I’m definitely in favour of splitting what we stabilise though, given that’s what I’m about to propose in the discussion

I'd also like to fix the Go environment bug since it'll probably require removing the synthetic target stuff (which will be a win as well for pants devs in the pants repo too)

it’ll probably require removing the synthetic target stuff

would be interesting to preserve a note somewhere if possible about what to consider when looking at synthetic targets to avoid pitfalls (if we’d call this case such 😉 )

@fast-nail-55400: yea, that would be good… let us know how we can help with that.

I'm not likely to hit a one week deadline for it since not my day job any more. Is there going to be a alpha release?

yes, there will be an alpha release

+1 to cutting 2.16 ASAP - let me know if I can help get stuff over the line 🙂

I would love to sneak https://github.com/pantsbuild/pants/pull/18132 in before 2.16.0 final is released 😄 if possible...

https://github.com/pantsbuild/pants/pull/18140 is an attempt to fix the non-local environment issue. It removes the need for a synthetic target, but does not actually yet fix the issue with running in a non-local (Docker in my testing) environment. Any advice on whether

EnvironmentName

or

EnvironmentField

(or some other type/rule) needs to be added in places? (The PR has a reproduction of the bug if anybody wants to take a look.)

(I just want 2.15.0rc3)

I realize I have a breaking change for the visibility backend I’d like to get in as well before we cut 2.16, to keep the break isolated in the 2.16.dev era.. for https://github.com/pantsbuild/pants/issues/17873#issuecomment-1407761256

okay so re the Go stuff, https://github.com/pantsbuild/pants/pull/18140 actually fixes Go running in the Docker environment apparently since the binary got built if I kept re-running

./pants package

enough times. The error I was seeing was from the Docker environment being flaky and input files not being fully visible to process being run which is flakiness in using the Docker environment, not anything particular (hopefully) to the Go backend.

@fast-nail-55400: was:

The error I was seeing was from the Docker environment being flaky and input files not being fully visible to process being run which is flakiness in using the Docker environment, not anything particular (hopefully) to the Go backend.

on macOS? if so: https://github.com/pantsbuild/pants/issues/18162#issuecomment-1421403119 … can take further discussion to the ticket or a new thread though

yes on macOS

regarding the release schedule: a minor fix to make the docs match our desired reality: https://github.com/pantsbuild/pants/pull/18234