i'll do that now

@aloof-angle-91616: recommend pushing the branch before making the notes changes so that you can see it go green

yes

(waiting on a rust recompile, i may have just figured out why the pre-commit hook kept saying i need to reformat rust files i haven't touched, but not quite sure yet)

i pushed the cherry-pick to 1.9.x: https://github.com/pantsbuild/pants/commit/1c1ce3815bcda7deb5ae76a4fd156a501e402a89

making the notes diff now

had to restart the py3 shard with a network error in a go contrib test

if it happens again i'll fix the flakiness

an entirely unrelated timeout (no output received in the last 10 minutes) on the py 3 shard again, so let's try one more time

unrelated as in the test that failed in the previous run passed, and this was in a totally different test

green means go

merging https://github.com/pantsbuild/pants/pull/6425 now then continuing with the hotfix release process (cherry-picking it and fixing VERSION)

the notes change was cherry-picked and the VERSION was bumped so i'm going to wait until someone says go to run the publish script

...or i guess until the binary builder shards complete on https://travis-ci.org/pantsbuild/pants/builds/422801519

to clarify i didn't realize that the hard way i just checked the release docs again

binary builder shards are green and dry run completed successfully so i'm gonna run the release script when someone says go

i'm on the master branch reset to the head of 1.9.x

@witty-crayon-22786 i'm only waiting in case there's some very obvious reason i don't know that i shouldn't do the release yet, no rush at all

Er

1.9.0rc2

like i said no rush

https://pypi.org/project/pantsbuild.pants/1.9.0rc2/ is up, pypi doesn't have it yet for pip BUT unlike

1.9.0rc0

it fails at

pantsbuild.pants

, not

pantsbuild.pants.contrib.buildgen

oh i think it's up now

i'm running the release test script

release test script passed

you'll hate me for this but there's one contributor I missed because I didn't realize the full author name given was just "Paul" (i thought this was an error in the script, and somehow both forgot about it and reverted the change instead of like, figuring it out if i thought there was an error in the script????). i'll make another PR with the contributors fix immediately. the first name "Paul" is not unique amongst contributors -- is it safe to assume that's how they want to be represented, or should I send them an email asking what name to use? just because looking at the list of contributors the only way someone would be able to know who "Paul" is referring to is to run the complex

git log

command we do in

contributors.sh

.

(this blocks the release email)

You can look at the name on GitHub