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/10/08 20:57:18 UTC
[beam-site] branch mergebot updated (3eb0e34 -> 7fb7725)
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 3eb0e34 This closes #576
add 5f1f846 Add deprecation notices
add 00f7adf Merge PR #567: [BEAM-4502] Add deprecation notices
add 9643460 [BEAM-5667] remove gradle files from website
add be422ea Merge PR#579: [BEAM-5667] remove gradle files from website
add 6f31911 [BEAM-5665] Exclude down website atrato.io from website checks
add 66ac84a Merge PR #578: [BEAM-5665] Exclude down website atrato.io from website checks
add 14d974b Merge Update internal links to use site.baseurl #576
new bf50ad5 Add instructions about how to sign and hash python wheels
new 7fb7725 This closes #568
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 (3eb0e34)
\
N -- N -- N refs/heads/mergebot (7fb7725)
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:
.github/PULL_REQUEST_TEMPLATE.md | 7 +++++++
.gradle/4.8/fileChanges/last-build.bin | Bin 1 -> 0 bytes
.gradle/4.8/fileHashes/fileHashes.bin | Bin 18547 -> 0 bytes
.gradle/4.8/fileHashes/fileHashes.lock | Bin 17 -> 0 bytes
.gradle/vcsWorkingDirs/gc.properties | 0
README.md | 5 +++++
Rakefile | 1 +
src/contribute/release-guide.md | 3 +++
8 files changed, 16 insertions(+)
delete mode 100644 .gradle/4.8/fileChanges/last-build.bin
delete mode 100644 .gradle/4.8/fileHashes/fileHashes.bin
delete mode 100644 .gradle/4.8/fileHashes/fileHashes.lock
delete mode 100644 .gradle/vcsWorkingDirs/gc.properties
[beam-site] 02/02: This closes #568
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 7fb77258dc98d09fdd77ff3e0d659bd91d752169
Merge: 14d974b bf50ad5
Author: Mergebot <me...@apache.org>
AuthorDate: Mon Oct 8 20:56:42 2018 +0000
This closes #568
src/contribute/release-guide.md | 3 +++
1 file changed, 3 insertions(+)
[beam-site] 01/02: Add instructions about how to sign and hash
python wheels
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 bf50ad55f2866c7e311f745dbdd1a8e403a410cf
Author: Boyuan Zhang <bo...@google.com>
AuthorDate: Mon Oct 1 15:09:01 2018 -0700
Add instructions about how to sign and hash python wheels
---
src/contribute/release-guide.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 6a5e1c4..76edfca 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -592,6 +592,9 @@ If you are interested in how it works, please refer to the [structure section](h
Please follow the [user guide](https://github.com/apache/beam-wheels#user-guide) to build python wheels.
+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 to sign and hash python wheels.
+
#### 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/)