You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2018/03/19 17:00:15 UTC
[beam-site] branch mergebot updated (c7523f5 -> 5bbcc4c)
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
discard c7523f5 This closes #401
add 04bf78e [BEAM-3852] Update slack channel link and slack invite for new channel.
new ebafac1 Update instructions on cryptographic hashes.
new 5bbcc4c This closes #402
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (c7523f5)
\
N -- N -- N refs/heads/mergebot (5bbcc4c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/contribute/release-guide.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.
[beam-site] 02/02: This closes #402
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit 5bbcc4c77207a10db050ed827dad0c6decacbfb6
Merge: 04bf78e ebafac1
Author: Mergebot <me...@apache.org>
AuthorDate: Mon Mar 19 09:59:58 2018 -0700
This closes #402
src/contribute/release-guide.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.
[beam-site] 01/02: Update instructions on cryptographic hashes.
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit ebafac13fa1aeca07c57bec2f7cbc2476ca1a5b1
Author: Robert Bradshaw <ro...@gmail.com>
AuthorDate: Sat Mar 17 01:25:13 2018 -0700
Update instructions on cryptographic hashes.
Per http://www.apache.org/dev/release-distribution#sigs-and-sums,
md5 is now officially discouraged as being too broken.
Removing SHA-1 as it is broken as well (though not nearly as badly).
SHA-512 is recommended.
---
src/contribute/release-guide.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 7feeba7..782b12b 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -300,11 +300,9 @@ Copy the source release to the dev repository of `dist.apache.org`.
1. Create hashes for source files and sign the python source file file
- sha1sum apache-beam-${VERSION}-source-release.zip > apache-beam-${VERSION}-source-release.zip.sha1
- md5sum apache-beam-${VERSION}-source-release.zip > apache-beam-${VERSION}-source-release.zip.md5
+ sha512sum apache-beam-${VERSION}-source-release.zip > apache-beam-${VERSION}-source-release.zip.sha512
gpg --armor --detach-sig apache-beam-${VERSION}-python.zip
- sha1sum apache-beam-${VERSION}-python.zip > apache-beam-${VERSION}-python.zip.sha1
- md5sum apache-beam-${VERSION}-python.zip > apache-beam-${VERSION}-python.zip.md5
+ sha512sum apache-beam-${VERSION}-python.zip > apache-beam-${VERSION}-python.zip.sha512
1. Add and commit all the files.
--
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.