lostluck commented on code in PR #28287: URL: https://github.com/apache/beam/pull/28287#discussion_r1320197180
########## website/www/site/content/en/contribute/release-guide.md: ########## @@ -167,101 +228,103 @@ Configure access to the [Apache Nexus repository](https://repository.apache.org/ </servers> </settings> -#### Submit your GPG public key into Ubuntu OpenPGP Key Server -In order to make yourself have right permission to stage java artifacts in Apache Nexus staging repository, -please submit your GPG public key into the [Ubuntu OpenPGP Key Server](https://keyserver.ubuntu.com/). +********** -You will need to use an ascii-armored version of your key. -This can be obtained by running `gpg --export --armor` and copying the whole block -(including `-----<START/END> PGP PUBLIC KEY BLOCK-----`). +### Handle Per Release tasks -#### Website development setup +#### Update base image dependencies for Python container images -Updating the Beam website requires submitting PRs to both the main `apache/beam` repo and the `apache/beam-site` repo. -The first contains reference manuals generated from SDK code, while the second updates the current release version number. +Tracked in Github issue https://github.com/apache/beam/issues/27944 -You should already have setup a local clone of `apache/beam`. -Setting up a clone of `apache/beam-site` is similar: +See instructions at: https://s.apache.org/beam-python-requirements-generate - $ git clone -b release-docs https://github.com/apache/beam-site.git - $ cd beam-site - $ git remote add <GitHub_user> [email protected]:<GitHub_user>/beam-site.git - $ git fetch --all - $ git checkout -b <my-branch> origin/release-docs +Ideally, do the update at least a week before the release cut, so that any issues +related to the update have time to surface. -Further instructions on website development on `apache/beam` is [here](https://github.com/apache/beam/blob/master/website). -Background information about how the website is updated can be found in [Beam-Site Automation Reliability](https://s.apache.org/beam-site-automation). +#### Update Go version used for container builds -#### Register to PyPI +Tracked in Github issue https://github.com/apache/beam/issues/27897 -Release manager needs to have an account with PyPI. -If you need one, [register at PyPI](https://pypi.python.org/account/register/). -You also need to be a maintainer (or an owner) of the [apache-beam](https://pypi.python.org/pypi/apache-beam) package in order to push a new release. -Ask on the mailing list for assistance. +Ideally, do the update at least a week before the release cut, so that any issues +related to the update have time to surface. -#### Login to DockerHub -If you are a member of the [`beam` DockerHub team](https://hub.docker.com/orgs/apache/teams/beam), run following command manually. -It will ask you to input your DockerHub ID and password if authorization info cannot be found from ~/.docker/config.json file. +#### Update the Java BOM -``` -docker login docker.io -``` +TODO(lostluck): Find instructions or associated issue/PRs (go/beam-issue/#####) Review Comment: Filed https://github.com/apache/beam/issues/28379 for now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
