[BEAM-10188] Add instructions to programmatically publish release to Github

[jphalip]

This fixes BEAM-10188.

See discussion in the dev@ list: https://lists.apache.org/thread.html/re367d262333078501c47856e9b8a0fc3fd7db60c2d2ebb181275481a%40%3Cdev.beam.apache.org%3E

This assumes that the blog post starts with "We are happy", which has been the case in most recent posts. But perhaps you'd like to tweak that?

[TheNeuralBit]

Thank you @jphalip! Just a few requests

[ibzib]

Thanks for doing this Julien!

Could we add this script to https://github.com/apache/beam/tree/master/release/src/main/scripts? Most of those scripts ask the user for input, for example

beam/release/src/main/scripts/build_release_candidate.sh

Lines 54 to 61 in e1963c1

	echo "================Setting Up Environment Variables==========="
	echo "Which release version are you working on: "
	read RELEASE
	RELEASE_BRANCH=release-${RELEASE}
	echo "Which release candidate number(e.g. 1) are you going to create: "
	read RC_NUM
	echo "Please enter your github username(ID): "
	read USER_GITHUB_ID

This way, they are self-contained and easy to use.

BTW, if you add the JIRA to the beginning of your PR title, they will be linked automatically.

[ibzib]

I didn't realize Brian had already reviewed... and we had almost the exact same comments 😆

[jphalip]

@ibzib @TheNeuralBit Thank you both for the feedback. I've moved the code to a separate script. All the variables used should already be set in script.config. Does that work?

[ibzib]

All the variables used should already be set in script.config. Does that work?

That's probably fine, but if that's the expectation we need to source script.config.

[jphalip]

Ok, I've loaded script.config. I've also added a confirmation message before submitting the API request.

[ibzib]

Looks good to me.

[TheNeuralBit]

LGTM as well. Thanks again @jphalip :)