You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apex.apache.org by th...@apache.org on 2017/11/10 16:01:30 UTC
[apex-site] branch master updated:
APEXCORE-794.ReleaseGuidelines-show-incorrect-sha-extension
This is an automated email from the ASF dual-hosted git repository.
thw pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apex-site.git
The following commit(s) were added to refs/heads/master by this push:
new 8da800f APEXCORE-794.ReleaseGuidelines-show-incorrect-sha-extension
8da800f is described below
commit 8da800fbd7116952a4e72fb993dd5d068f3657aa
Author: Ananth <an...@gmail.com>
AuthorDate: Thu Nov 9 06:43:21 2017 +1100
APEXCORE-794.ReleaseGuidelines-show-incorrect-sha-extension
---
.gitignore | 3 ++-
src/md/release.md | 18 ++++++++++++++----
src/md/verification.md | 4 ++--
3 files changed, 18 insertions(+), 7 deletions(-)
diff --git a/.gitignore b/.gitignore
index f3af33d..d30f94e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,4 +2,5 @@
node_modules
bower_components
content
-docs/
\ No newline at end of file
+docs/
+.idea/
\ No newline at end of file
diff --git a/src/md/release.md b/src/md/release.md
index 39f3585..d257a85 100644
--- a/src/md/release.md
+++ b/src/md/release.md
@@ -105,6 +105,7 @@ Prerequisites:
- GPG key needs to be in https://dist.apache.org/repos/dist/release/apex/KEYS
- Credentials for `apache.staging.https` server distribution management in `~/.m2/settings.xml`
- Tag pushed to ASF git
+ - The correct version of the JDK is installed and maven is using the right java version
Build and deploy release candidate from RC tag:
@@ -113,6 +114,15 @@ git checkout "v${rv}-RC1"
git clean -d -f
mvn clean apache-rat:check deploy -Papache-release -Pall-modules -DskipTests
```
+Some recent versions of the GPG might result in the following error message when the above maven deploy command is invoked.
+```
+gpg: signing failed: Inappropriate ioctl for device
+```
+Setting the GPG terminal fixes this. GPG terminal can be set using
+```
+GPG_TTY=$(tty)
+export GPG_TTY
+```
Confirm no archives are included in source release (rat:check reports them in target/rat.txt but does not fail the build):
```
@@ -142,8 +152,8 @@ RNAME=apache-apex-malhar-${rv}
cd target
md5sum ${RNAME}-source-release.tar.gz > ${RNAME}-source-release.tar.gz.md5
md5sum ${RNAME}-source-release.zip > ${RNAME}-source-release.zip.md5
-shasum -a 512 ${RNAME}-source-release.tar.gz > ${RNAME}-source-release.tar.gz.sha
-shasum -a 512 ${RNAME}-source-release.zip > ${RNAME}-source-release.zip.sha
+shasum -a 512 ${RNAME}-source-release.tar.gz > ${RNAME}-source-release.tar.gz.sha512
+shasum -a 512 ${RNAME}-source-release.zip > ${RNAME}-source-release.zip.sha512
gpg --yes --armor --output ${RNAME}-source-release.tar.gz.asc --detach-sig ${RNAME}-source-release.tar.gz
gpg --yes --armor --output ${RNAME}-source-release.zip.asc --detach-sig ${RNAME}-source-release.zip
```
@@ -218,10 +228,10 @@ After [publishing the site](https://github.com/apache/apex-site/tree/master#cont
## Voting
Vote call sample:
-http://mail-archives.apache.org/mod_mbox/apex-dev/201605.mbox/%3CCAKJfLDPr3CBCfstQJWjchG-ZEYw5P%2Bwv5jN0tfy3EL%2BU%3DBUQgQ%40mail.gmail.com%3E
+https://lists.apache.org/thread.html/bee03103dfdd94ffeb9dafdd2e0e468609948f59649534db2d99b464@%3Cdev.apex.apache.org%3E
Vote result:
-http://mail-archives.apache.org/mod_mbox/apex-dev/201605.mbox/%3CCAKJfLDNQzMN4zcuTHosU%2BCepF38A_2VL03GOYSc2%3DxxV-9iqMw%40mail.gmail.com%3E
+https://lists.apache.org/thread.html/2887965dba350e181d06aa02af19d8d47c82eb6f0b47eef8dce14fe8@%3Cdev.apex.apache.org%3E
Note that the vote result email should have the subject prefixed with `[RESULT]`.
diff --git a/src/md/verification.md b/src/md/verification.md
index eb0e870..a670321 100644
--- a/src/md/verification.md
+++ b/src/md/verification.md
@@ -36,14 +36,14 @@ Verify integrity of tar.gz file:
```bash
gpg --verify $APEX_RELEASE_CANDIDATE-source-release.tar.gz.asc
md5sum --check $APEX_RELEASE_CANDIDATE-source-release.tar.gz.md5
-sha512sum --check $APEX_RELEASE_CANDIDATE-source-release.tar.gz.sha
+shasum -a 512 --check $APEX_RELEASE_CANDIDATE-source-release.tar.gz.sha512
```
Verify integrity of .zip file:
```bash
gpg --verify $APEX_RELEASE_CANDIDATE-source-release.zip.asc
md5sum --check $APEX_RELEASE_CANDIDATE-source-release.zip.md5
-sha512sum --check $APEX_RELEASE_CANDIDATE-source-release.zip.sha
+shasum -a 512 --check $APEX_RELEASE_CANDIDATE-source-release.zip.sha512
```
## Source code verification
--
To stop receiving notification emails like this one, please contact
['"commits@apex.apache.org" <co...@apex.apache.org>'].