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 ad9b65dbfdb0c98c4f381b05ede31416a5f7f95b Author: Melissa Pashniak <meliss...@google.com> AuthorDate: Wed Oct 3 18:37:20 2018 -0700 Edit suggestions --- src/contribute/release-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md index b8cd62c..6a5e1c4 100644 --- a/src/contribute/release-guide.md +++ b/src/contribute/release-guide.md @@ -180,9 +180,9 @@ When contributors resolve an issue in JIRA, they are tagging it with a release t __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 release cut date (today’s date) as the `Start Date`, and choose `Add`. -1. At the end of the release, in the same page mark the recently released version as released. (Use the `...` menu and choose `Release`). +1. In JIRA, navigate to [`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 after the version currently underway, select the release cut date (today’s date) as the `Start Date`, and choose `Add`. +1. At the end of the release, go to the same page and mark the recently released version as released. Use the `...` menu and choose `Release`. ### Triage release-blocking issues in JIRA