[beam-site] 03/04: Add instructions about the permission of creating new version in JIRA

[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`.