This is an automated email from the ASF dual-hosted git repository.
apilloud pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/master by this push:
new 0e06e16 Update release guide with feedback from 2.12.0 release
new b529db9 Merge pull request #8315: Update release guide with feedback
from 2.12.0 release
0e06e16 is described below
commit 0e06e165e9d9c9c1d6405313096cd1f257176314
Author: Andrew Pilloud <apill...@google.com>
AuthorDate: Mon Apr 15 11:21:41 2019 -0700
Update release guide with feedback from 2.12.0 release
---
.../src/main/scripts/build_release_candidate.sh | 3 +-
.../src/main/scripts/sign_hash_python_wheels.sh | 8 ++++--
website/src/contribute/release-guide.md | 32 ++++++++++++----------
3 files changed, 26 insertions(+), 17 deletions(-)
diff --git a/release/src/main/scripts/build_release_candidate.sh
b/release/src/main/scripts/build_release_candidate.sh
index c9e5139..8055d6e 100755
--- a/release/src/main/scripts/build_release_candidate.sh
+++ b/release/src/main/scripts/build_release_candidate.sh
@@ -290,4 +290,5 @@ echo " - add new release download links like commit: "
echo "
https://github.com/apache/beam-site/commit/29394625ce54f0c5584c3db730d3eb6bf365a80c#diff-abdcc989e94369c2324cf64b66659eda";
echo " - update last release download links from release to archive like
commit: "
echo "
https://github.com/apache/beam-site/commit/6b9bdb31324d5c0250a79224507da0ea7ae8ccbf#diff-abdcc989e94369c2324cf64b66659eda";
-echo "3.Start the review-and-vote thread on the dev@ mailing list."
+echo "3.You need to build Python Wheels."
+echo "4.Start the review-and-vote thread on the dev@ mailing list."
diff --git a/release/src/main/scripts/sign_hash_python_wheels.sh
b/release/src/main/scripts/sign_hash_python_wheels.sh
index d521ca4..05b703d 100755
--- a/release/src/main/scripts/sign_hash_python_wheels.sh
+++ b/release/src/main/scripts/sign_hash_python_wheels.sh
@@ -49,6 +49,10 @@ fi
svn co ${BEAM_SVN_DIR}/${VERSION}
cd ${VERSION}/${PYTHON_ARTIFACTS_DIR}
+
+echo "Fetch wheels artifacts"
+gsutil cp -r gs://beam-wheels-staging/apache_beam-${VERSION}\*.whl .
+
echo "Start signing and hashing python wheels artifacts"
rm *.whl.asc || true
rm *.whl.sha512 ||true
@@ -56,7 +60,7 @@ for artifact in *.whl; do
gpg --local-user ${SIGNING_KEY} --armor --detach-sig $artifact
sha512sum $artifact > ${artifact}.sha512
done
-svn add --force *
+svn add --force .
svn commit --no-auth-cache
-rm -rf ~/${VERSION}
\ No newline at end of file
+rm -rf ~/${VERSION}
diff --git a/website/src/contribute/release-guide.md
b/website/src/contribute/release-guide.md
index 4467533..5de5eaf 100644
--- a/website/src/contribute/release-guide.md
+++ b/website/src/contribute/release-guide.md
@@ -485,8 +485,6 @@ The core of the release process is the build-vote-fix
cycle. Each cycle produces
For this step, we recommend you using automation script to create a RC, but
you still can perform all steps manually if you want.
-*BUT* the final step of rc creation is `Build and stage python wheels`, which
need to done manually.
-
### Run build_release_candidate.sh to create RC
* Script:
[build_release_candidate.sh](https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh)
@@ -511,6 +509,8 @@ For this step, we recommend you using automation script to
create a RC, but you
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.
+
### Run all steps manually
@@ -654,6 +654,12 @@ Please follow the [user
guide](https://github.com/apache/beam-wheels#user-guide)
Once all python wheels have been staged
[dist.apache.org](https://dist.apache.org/repos/dist/dev/beam/),
please run
[./sign_hash_python_wheels.sh](https://github.com/apache/beam/blob/master/release/src/main/scripts/sign_hash_python_wheels.sh)
to sign and hash python wheels.
+### Write the Beam blog post and create a pull request
+
+Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged.
+
+*Tip:* Use git log to find contributors to the releases. (e.g: `git log
--pretty='%aN' ^v2.10.0 v2.11.0 | sort | uniq`).
+
#### Checklist to proceed to the next step
1. Maven artifacts deployed to the staging repository of
[repository.apache.org](https://repository.apache.org/content/repositories/)
@@ -690,21 +696,25 @@ Start the review-and-vote thread on the dev@ mailing
list. Here’s an email tem
* the official Apache source release to be deployed to dist.apache.org
[2], which is signed with the key with fingerprint FFFFFFFF [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v1.2.3-RC3" [5],
- * website pull request listing the release and publishing the API
reference manual [6].
+ * website pull request listing the release [6], publishing the API
reference manual [7], and the blog post [8].
* Java artifacts were built with Maven MAVEN_VERSION and OpenJDK/Oracle
JDK JDK_VERSION.
* Python artifacts are deployed along with the source release to the
dist.apache.org [2].
+ * Validation sheet with a tab for 1.2.3 release to help with validation
[9].
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
Thanks,
Release Manager
- [1] link
- [2] link
+ [1] https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=...
+ [2] https://dist.apache.org/repos/dist/dev/beam/1.2.3/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
- [4] link
- [5] link
- [6] link
+ [4] https://repository.apache.org/content/repositories/orgapachebeam-NNNN/
+ [5] https://github.com/apache/beam/tree/v1.2.3-RC3
+ [6] https://github.com/apache/beam/pull/...
+ [7] https://github.com/apache/beam-site/pull/...
+ [8] https://github.com/apache/beam/pull/...
+ [9]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=...
If there are any issues found in the release candidate, reply on the vote
thread to cancel the vote. There’s no need to wait 72 hours. Proceed to the
`Fix Issues` step below and address the problem. However, some issues don’t
require cancellation. For example, if an issue is found in the website pull
request, just correct it on the spot and the vote can continue as-is.
@@ -1056,12 +1066,6 @@ Announce on the release on the user@ mailing list,
listing major improvements an
Announce the release on the annou...@apache.org mailing list.
-### Beam blog
-
-Major or otherwise important releases should have a blog post. Write one if
needed for this particular release. Minor releases that don’t introduce new
major functionality don’t necessarily need to be blogged.
-
-*Tip:* Use git log to find contributors to the releases. (e.g: `git log
--pretty='%aN' ^v2.10.0 v2.11.0 | sort | uniq`).
-
### Social media
Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors
to do the same.
