This is an automated email from the ASF dual-hosted git repository.
tbouron pushed a commit to branch website
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/website by this push:
new d60e892 remove references to MD5/SHA1 from release process description
new 9a9090a Merge pull request #303 from geomacy/website
d60e892 is described below
commit d60e892b5ba67516d052ddb4894e9295493b1f31
Author: Geoff Macartney
AuthorDate: Sat Jan 25 22:02:31 2020 +
remove references to MD5/SHA1 from release process description
Meant to do this after https://github.com/apache/brooklyn-dist/pull/150
---
.../committers/release-process/make-release-artifacts.md | 2 +-
developers/committers/release-process/prerequisites.md | 2 --
developers/committers/release-process/publish-temp.md | 2 +-
developers/committers/release-process/publish.md | 10 --
.../committers/release-process/verify-release-artifacts.md | 8 +++-
5 files changed, 9 insertions(+), 15 deletions(-)
diff --git a/developers/committers/release-process/make-release-artifacts.md
b/developers/committers/release-process/make-release-artifacts.md
index 730a7cb..a408cb7 100644
--- a/developers/committers/release-process/make-release-artifacts.md
+++ b/developers/committers/release-process/make-release-artifacts.md
@@ -46,6 +46,6 @@ The release script will:
3. Invoke Maven to build the source code (including running unit tests), and
deploy artifacts to a Maven remote
repository
4. Save the .tar.gz and .zip artifacts produced by the build of `brooklyn-dist`
-5. For each of the produced files, produce MD5, SHA1, SHA256 and GnuPG
signatures
+5. For each of the produced files, produce SHA256 and GnuPG signatures
At the end of the script, it will show you the files it has produced and their
location.
diff --git a/developers/committers/release-process/prerequisites.md
b/developers/committers/release-process/prerequisites.md
index 0323428..399416d 100644
--- a/developers/committers/release-process/prerequisites.md
+++ b/developers/committers/release-process/prerequisites.md
@@ -44,8 +44,6 @@ The following software packages are required during the
build. Make sure you hav
- `gnupg2`, and `gnupg-agent` if it is packaged separately (it is on Ubuntu
Linux)
- `pinentry` for secure entry of GPG passphrases. If you are building remotely
on a Linux machine, `pinentry-curses` is
recommended; building on a mac, `port install pinentry-mac` is recommended.
-- `md5sum` and `sha1sum` - these are often present by default on Linux, but
not on Mac;
- `port install md5sha1sum` should remedy that.
- if `gpg` does not resolve (it is needed for maven), create an alias or
script pointing at `gpg2 "$@"`
- the `mmv` command (usually in a package named `mmv`) will help with the
final steps of the release process
diff --git a/developers/committers/release-process/publish-temp.md
b/developers/committers/release-process/publish-temp.md
index 278ce73..a0fe07b 100644
--- a/developers/committers/release-process/publish-temp.md
+++ b/developers/committers/release-process/publish-temp.md
@@ -34,7 +34,7 @@ mkdir apache-brooklyn-${VERSION_NAME}-rc${RC_NUMBER}
{% endhighlight %}
Copy into this directory all of the artifacts from the previous step - `-src`
and `-bin`, `.tar.gz`, `.zip` and `.rpm`,
-and all associated `.md5`, `.sha1`, `.sha256` and `.asc` signatures. Then
commit:
+and all associated `.sha256` and `.asc` signatures. Then commit:
{% highlight bash %}
svn add apache-brooklyn-${VERSION_NAME}-rc${RC_NUMBER}
diff --git a/developers/committers/release-process/publish.md
b/developers/committers/release-process/publish.md
index 86211e8..fa865c8 100644
--- a/developers/committers/release-process/publish.md
+++ b/developers/committers/release-process/publish.md
@@ -33,7 +33,7 @@ mkdir apache-brooklyn-${VERSION_NAME}
{% endhighlight %}
Refer back to the pre-release area Subversion (see [Publish to the staging
area](publish-temp.html)), and copy all of
-the release candidate artifacts - `-src` and `-bin`, `.tar.gz` and `.zip`, and
all associated `.md5`, `.sha1`, `.sha256`
+the release candidate artifacts - `-src` and `-bin`, `.tar.gz` and `.zip`, and
all associated `.sha256`
and `.asc` signatures - into this new folder.
Rename all of the files to remove the `-rcN` designation:
@@ -45,7 +45,7 @@ for f in *; do mv $f ${f//-rc${RC_NUMBER}/}; done
The hash files will need patching to refer to the filenames without the `-rcN`
designation:
{% highlight bash %}
-sed -i.bak 's/-rc'$RC_NUMBER'-/-/' *.md5 *.sha1 *.sha256
+sed -i.bak 's/-rc'$RC_NUMBER'-/-/' *.sha256
rm -f *.bak
{% endhighlight %}
@@ -54,9 +54,7 @@ Note that the PGP signatures do not embed the filename so
they do not need to be
As a final check, re-test the hashes and signatures:
{% highlight bash %}
-for artifact in $(find * -type
