You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by mz...@apache.org on 2019/04/11 18:52:41 UTC
[mesos] branch master updated: Documented requesting JIRA
permission in the release guide.
This is an automated email from the ASF dual-hosted git repository.
mzhu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git
The following commit(s) were added to refs/heads/master by this push:
new cb4c966 Documented requesting JIRA permission in the release guide.
cb4c966 is described below
commit cb4c9660eecae59bc2acbeb37ab19214f7b0e19b
Author: Meng Zhu <mz...@mesosphere.io>
AuthorDate: Thu Apr 11 11:50:28 2019 -0700
Documented requesting JIRA permission in the release guide.
---
docs/release-guide.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/release-guide.md b/docs/release-guide.md
index 83d48e1..a3ad266 100644
--- a/docs/release-guide.md
+++ b/docs/release-guide.md
@@ -72,6 +72,8 @@ This guide describes the process of doing an official release of Mesos.
to track the progress of targeted issues as the release date approaches. This
JIRA filter may be useful (`<X.Y.Z>` is the release version):
`project = MESOS AND "Target Version/s" = <X.Y.Z> AND (fixVersion != <X.Y.Z> OR fixVersion = EMPTY)`
+ Note, you may need to request permission to create shared dashboard and filters by opening
+ an Apache INFRA ticket.
**PROTIP:** Use `bulk edit` option in JIRA to move the tickets and make sure
to **uncheck** the option that emails everyone about the move to avoid