[mesos-site] branch asf-site updated: Updated the website built from mesos SHA: cb4c966.

[git-site-role]

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

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mesos-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 8666808  Updated the website built from mesos SHA: cb4c966.
8666808 is described below

commit 86668085a5d3a0648b7e383a9cbae3ffbba75b69
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Apr 11 19:22:48 2019 +0000

    Updated the website built from mesos SHA: cb4c966.
---
 content/documentation/latest/release-guide/index.html | 4 +++-
 content/documentation/release-guide/index.html        | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/content/documentation/latest/release-guide/index.html 
b/content/documentation/latest/release-guide/index.html
index 7bef4d6..1e27ab5 100644
--- a/content/documentation/latest/release-guide/index.html
+++ b/content/documentation/latest/release-guide/index.html
@@ -176,7 +176,9 @@ or <code>Target Version</code> as the release version to 
the next release versio
 <a 
href="https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329720";>(example)</a>
 to track the progress of targeted issues as the release date approaches. This
 JIRA filter may be useful (<code>&lt;X.Y.Z&gt;</code> is the release version):
-<code>project = MESOS AND "Target Version/s" = &lt;X.Y.Z&gt; AND (fixVersion 
!= &lt;X.Y.Z&gt; OR fixVersion = EMPTY)</code></p>
+<code>project = MESOS AND "Target Version/s" = &lt;X.Y.Z&gt; AND (fixVersion 
!= &lt;X.Y.Z&gt; OR fixVersion = EMPTY)</code>
+Note, you may need to request permission to create shared dashboard and 
filters by opening
+an Apache INFRA ticket.</p>
 
 <p><strong>PROTIP:</strong> Use <code>bulk edit</code> option in JIRA to move 
the tickets and make sure
 to <strong>uncheck</strong> the option that emails everyone about the move to 
avoid
diff --git a/content/documentation/release-guide/index.html 
b/content/documentation/release-guide/index.html
index 99c465a..0a853d0 100644
--- a/content/documentation/release-guide/index.html
+++ b/content/documentation/release-guide/index.html
@@ -176,7 +176,9 @@ or <code>Target Version</code> as the release version to 
the next release versio
 <a 
href="https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329720";>(example)</a>
 to track the progress of targeted issues as the release date approaches. This
 JIRA filter may be useful (<code>&lt;X.Y.Z&gt;</code> is the release version):
-<code>project = MESOS AND "Target Version/s" = &lt;X.Y.Z&gt; AND (fixVersion 
!= &lt;X.Y.Z&gt; OR fixVersion = EMPTY)</code></p>
+<code>project = MESOS AND "Target Version/s" = &lt;X.Y.Z&gt; AND (fixVersion 
!= &lt;X.Y.Z&gt; OR fixVersion = EMPTY)</code>
+Note, you may need to request permission to create shared dashboard and 
filters by opening
+an Apache INFRA ticket.</p>
 
 <p><strong>PROTIP:</strong> Use <code>bulk edit</code> option in JIRA to move 
the tickets and make sure
 to <strong>uncheck</strong> the option that emails everyone about the move to 
avoid