This is an automated email from the ASF dual-hosted git repository.

pabloem pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/master by this push:
     new 65e66e6  Update release guide instructions.
     new 5076255  Merge pull request #13012 from ibzib/docker-push-release - 
Update release guide instructions.
65e66e6 is described below

commit 65e66e631be0c002ef388f48fc0dc98e5ca9e414
Author: Kyle Weaver <[email protected]>
AuthorDate: Mon Oct 5 12:41:40 2020 -0700

    Update release guide instructions.
    
    Pushing a Docker release now requires INFRA to grant permission, not Beam 
PMC.
---
 website/www/site/content/en/contribute/release-guide.md | 14 +-------------
 1 file changed, 1 insertion(+), 13 deletions(-)

diff --git a/website/www/site/content/en/contribute/release-guide.md 
b/website/www/site/content/en/contribute/release-guide.md
index d23b5d2..3de11ea 100644
--- a/website/www/site/content/en/contribute/release-guide.md
+++ b/website/www/site/content/en/contribute/release-guide.md
@@ -219,20 +219,8 @@ After successful login, authorization info will be stored 
at ~/.docker/config.js
    "auth": "xxxxxx"
 }
 ```
-Release managers should have push permission; please ask for help at dev@.
-```
-From: Release Manager
-To: [email protected]
-Subject: DockerHub Push Permission
-
-Hi DockerHub Admins
+Release managers should have push permission; request membership in the 
[`beammaintainers` 
team](https://hub.docker.com/orgs/apache/teams/beammaintainers) by filing a 
JIRA with the Apache Infrastructure team, like 
[INFRA-20900](https://issues.apache.org/jira/browse/INFRA-20900).
 
-I need push permission to proceed with release, can you please add me to 
maintainer team?
-My docker hub ID is: xxx
-
-Thanks,
-Release Manager
-```
 ### Create a new version in JIRA
 
 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:

Reply via email to