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/09/07 23:53:40 UTC
[beam-site] branch mergebot updated (c54d1bb -> 9cc9d43)
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.
from c54d1bb This closes #548
add 32712a7 Prepare repository for deployment.
new 40ff26b Add instructions about how to configure github https access
new 6ebddad Add instructions about how to close apache staging repo
new 2be4f66 Add instructions about the permission of creating new version in JIRA
new 9cc9d43 This closes #550
The 4 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:
content/contribute/portability/index.html | 8 ++++----
src/contribute/release-guide.md | 12 +++++++++++-
2 files changed, 15 insertions(+), 5 deletions(-)
[beam-site] 03/04: Add instructions about the permission of
creating new version in JIRA
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 2be4f663d72045322f2ea70003d1a1ac1e422650
Author: Boyuan Zhang <bo...@google.com>
AuthorDate: Fri Sep 7 16:17:38 2018 -0700
Add instructions about the permission of creating new version in JIRA
---
src/contribute/release-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 8807ff9..2c66080 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -178,7 +178,7 @@ Release manager needs to have an account with PyPI. If you need one, [register a
When contributors resolve an issue in JIRA, they are tagging it with a release that will contain their changes. With the release currently underway, new issues should be resolved against a subsequent future release. Therefore, you should create a release item for this subsequent release, as follows:
-Attention: Only committer has permission to perform this.
+__Attention__: Only PMC has permission to perform this. If you are not a PMC, please ask for help in dev@ mailing list.
1. In JIRA, navigate to the [`Beam > Administration > Versions`](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions).
1. Add a new release: choose the next minor version number compared to the one currently underway, select today’s date as the `Start Date`, and choose `Add`.
[beam-site] 04/04: This closes #550
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 9cc9d439229077aeafd800ed01718d46fecc80a7
Merge: 32712a7 2be4f66
Author: Mergebot <me...@apache.org>
AuthorDate: Fri Sep 7 23:52:56 2018 +0000
This closes #550
src/contribute/release-guide.md | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
[beam-site] 01/04: Add instructions about how to configure github
https access
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 40ff26b9b24da4b6f3de97bc7628e737babf3ff5
Author: Boyuan Zhang <bo...@google.com>
AuthorDate: Fri Sep 7 15:59:59 2018 -0700
Add instructions about how to configure github https access
---
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 dca62c2..298e63b 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -71,6 +71,9 @@ Before your first release, you should perform one-time configuration steps. This
To prepare for each release, you should audit the project status in the JIRA issue tracker, and do necessary bookkeeping. Finally, you should create a release branch from which individual release candidates will be built.
+__NOTE__: If you are using [GitHub two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/) and haven't configure HTTPS access,
+please follow [the guide](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) to configure command line access.
+
### One-time setup instructions
#### GPG Key
[beam-site] 02/04: Add instructions about how to close apache
staging repo
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 6ebddadfab965962e44b1eaaf501048d843b4370
Author: Boyuan Zhang <bo...@google.com>
AuthorDate: Fri Sep 7 16:11:49 2018 -0700
Add instructions about how to close apache staging repo
---
src/contribute/release-guide.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 298e63b..8807ff9 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -161,6 +161,10 @@ Configure access to the [Apache Nexus repository](http://repository.apache.org/)
</servers>
</settings>
+#### Submit your GPG public key into MIT PGP Public Key Server
+In order to make yourself have right permission to stage java artifacts in Apache Nexus staging repository,
+please submit your GPG public key into [MIT PGP Public Key Server](http://pgp.mit.edu:11371/).
+
#### Website development setup
Prepare to update the Beam website by following the [website development
@@ -440,6 +444,9 @@ For this step, we recommend you using automation script to create a RC, but you
* Tasks included
1. Run gradle release to create rc tag and push source release into github repo.
1. Run gradle publish to push java artifacts into Maven staging repo.
+
+ __NOTE__: In order to public staging artifacts, you need to goto the staging repo to close the staging repository on Apache Nexus.
+ When prompted for a description, enter “Apache Beam, version X, release candidate Y”.
1. Stage source release into dist.apache.org dev [repo](https://dist.apache.org/repos/dist/dev/beam/).
1. Stage,sign and hash python binaries into dist.apache.ord dev repo python dir
1. Create a PR to update beam-site, changes includes: