[
https://issues.apache.org/jira/browse/BEAM-10048?focusedWorklogId=436092&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-436092
]
ASF GitHub Bot logged work on BEAM-10048:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/20 16:40
Start Date: 21/May/20 16:40
Worklog Time Spent: 10m
Work Description: ibzib commented on a change in pull request #11764:
URL: https://github.com/apache/beam/pull/11764#discussion_r428774392
##########
File path: website/www/site/content/en/contribute/release-guide.md
##########
@@ -583,189 +582,44 @@ For this step, we recommend you using automation script
to create a RC, but you
1. Stage source release into dist.apache.org dev
[repo](https://dist.apache.org/repos/dist/dev/beam/).
1. Stage,sign and hash python binaries into dist.apache.ord dev repo python
dir
1. Stage SDK docker images to [docker hub Apache
organization](https://hub.docker.com/search?q=apache%2Fbeam&type=image).
- 1. Create a PR to update beam and beam-site, changes includes:
+ 1. Create a PR to update beam-site, changes includes:
* Copy python doc into beam-site
* Copy java doc into beam-site
- * Update release version into
[_config.yml](https://github.com/apache/beam/blob/master/website/_config.yml).
#### Tasks you need to do manually
- 1. Add new release into `website/src/get-started/downloads.md`.
- 1. Update last release download links in
`website/src/get-started/downloads.md`.
- 1. Update `website/src/.htaccess` to redirect to the new version.
- 1. Build and stage python wheels.
+ 1. Verify the script worked.
+ 1. Verify that the source and Python binaries are present in
[dist.apache.org](https://dist.apache.org/repos/dist/dev/beam).
+ 1. Verify Docker images are published. How to find images:
+ 1. Visit
[https://hub.docker.com/u/apache](https://hub.docker.com/search?q=apache%2Fbeam&type=image)
+ 2. Visit each repository and navigate to *tags* tab.
+ 3. Verify images are pushed with tags: ${RELEASE}_rc{RC_NUM}
+ 1. Verify that third party licenses are included in Docker containers by
logging in to the images.
+ - For Python SDK images, there should be around 80 ~ 100
dependencies.
+ Please note that dependencies for the SDKs with different Python
versions vary.
+ Need to verify all Python images by replacing `${ver}` with each
supported Python version `X.Y`.
+ ```
+ docker run -it --entrypoint=/bin/bash
apache/beam_python${ver}_sdk:${RELEASE}_rc{RC_NUM}
+ ls -al /opt/apache/beam/third_party_licenses/ | wc -l
+ ```
+ - For Java SDK images, there should be around 1400 dependencies.
+ ```
+ docker run -it --entrypoint=/bin/bash
apache/beam_java_sdk:${RELEASE}_rc{RC_NUM}
+ ls -al /opt/apache/beam/third_party_licenses/ | wc -l
+ ```
1. Publish staging artifacts
- 1. Go to the staging repo to close the staging repository on [Apache
Nexus](https://repository.apache.org/#stagingRepositories).
+ 1. Go to the staging repo to close the staging repository on [Apache
Nexus](https://repository.apache.org/#stagingRepositories).
Review comment:
I added more detailed instructions.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 436092)
Time Spent: 1h 10m (was: 1h)
> Remove "manual steps" from release guide.
> -----------------------------------------
>
> Key: BEAM-10048
> URL: https://issues.apache.org/jira/browse/BEAM-10048
> Project: Beam
> Issue Type: Improvement
> Components: build-system, website
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: P2
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> release-guide.md contains most of the same instructions as
> build_release_candidate.sh ("(Alternative) Run all steps manually"). This is
> not ideal:
> - Mirroring the instructions in release-guide.md doesn't add any value.
> - Every single change to the process requires two identical changes to each
> file, and this makes it unnecessarily difficult to keep the two in sync.
> - All the extra instructions make release-guide.md harder to read, obscuring
> information that the release manager actually does need to know.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
