A few related release logistics/questions: • https://github.com/pantsbuild/pants/pull/22607 looks like it is going to be a high priority thing at $DAYJOB ; so I volunteered to do 2.29.x release management as a matter of self interest (issue created) • Does anyone happen to regularly use

PANTS_BOOTSTRAP_URLS

(or some more obvious option I am missing) to distribute your own version of Pants internally? • @fast-nail-55400 https://github.com/pantsbuild/pants/tree/2.28.x has not had any changes for the past two weeks. Were you waiting for anything before the .0? Would you like any help?

• Does anyone happen to regularly use

PANTS_BOOTSTRAP_URLS

(or some more obvious option I am missing) to distribute your own version of Pants internally?

Not regularly but I did successfully test a workflow in a pants fork where I ran a modified version of the standard Pants release workflow to release from the fork with a "local" version number, and then consume that version in a repo.