This is an automated email from the ASF dual-hosted git repository.
ethanli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/master by this push:
new 4c69b96 MINOR: create a checklist for testing a new Storm release
(#3161)
4c69b96 is described below
commit 4c69b96307bf5f0464cab6c5333171dadf939c97
Author: Meng Li (Ethan) <[email protected]>
AuthorDate: Thu Oct 31 11:03:22 2019 -0500
MINOR: create a checklist for testing a new Storm release (#3161)
* create a checklist for testing a new Storm release
* add link to dev-tools/rc and remove MD5 file check
---
RELEASING.md | 26 +++++++++++++++++++++++---
dev-tools/rc/verify-release-file.sh | 15 ---------------
2 files changed, 23 insertions(+), 18 deletions(-)
diff --git a/RELEASING.md b/RELEASING.md
index 06f2012..6affa3a 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -1,7 +1,6 @@
-# Committer documentation
+# Release
-This document summarizes information relevant to Storm committers. It
includes information about
-the Storm release process.
+This document includes information about the Storm release process.
---
@@ -85,3 +84,24 @@ gpg --print-md SHA512 RELEASE_NOTES.html >
RELEASE_NOTES.html.sha512
2. Delete the staged distribution files from
https://dist.apache.org/repos/dist/dev/storm/
3. Delete the git tag.
+
+# How to vote on a release candidate
+
+We encourage everyone to review and vote on a release candidate to make an
Apache Storm release more reliable and trustworthy.
+
+Below is a checklist that one could do to review a release candidate.
+Please note this list is not exhaustive and only includes some of the common
steps. Feel free to add your own tests.
+
+1. Verify files such as *.asc, *.sha512; some scripts are available under
`dev-tools/rc` to help with it;
+2. Build Apache Storm source code and run unit tests, create an Apache Storm
distribution;
+3. Set up a standalone cluster using apache-storm-xxx.zip,
apache-storm-xxx.tar.gz, the Apache Storm distribution created from step 2,
separately;
+4. Launch WordCountTopology and ThroughputVsLatency topology and check logs,
UI metrics, etc;
+5. Test basic UI functionalities such as jstack, heap dump, deactivate,
activate, rebalance, change log level, log search, kill topology;
+6. Test basic CLI such as kill, list, deactivate, deactivate, rebalance, etc.
+
+It's also preferable to set up a standalone secure Apache Storm cluster and
test basic funcionalities on it.
+
+Don't feel the pressure to do everything listed above. After you finish your
review, reply to the corresponding email thread with your vote, summarize the
work you have performed and elaborate the issues
+you have found if any. Also please feel free to update the checklist if you
think anything important is missing there.
+
+Your contribution is very much appreciated.
\ No newline at end of file
diff --git a/dev-tools/rc/verify-release-file.sh
b/dev-tools/rc/verify-release-file.sh
index 2e33965..3e6a869 100755
--- a/dev-tools/rc/verify-release-file.sh
+++ b/dev-tools/rc/verify-release-file.sh
@@ -34,21 +34,6 @@ else
echo 'Signature seems not correct'
fi
-# checking MD5
-GPG_MD5_FILE="/tmp/${TARGET_FILE}_GPG.md5"
-gpg --print-md MD5 ${TARGET_FILE} > ${GPG_MD5_FILE}
-MD5_TARGET_FILE="${TARGET_FILE}.md5"
-
-echo ">> checking MD5 file... (${MD5_TARGET_FILE})"
-diff ${GPG_MD5_FILE} ${MD5_TARGET_FILE}
-
-if [ $? -eq 0 ];
-then
- echo 'MD5 file is correct'
-else
- echo 'MD5 file is not correct'
-fi
-
# checking SHA
GPG_SHA_FILE="/tmp/${TARGET_FILE}_GPG.sha512"
gpg --print-md SHA512 ${TARGET_FILE} > ${GPG_SHA_FILE}
