You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by al...@apache.org on 2016/11/03 21:49:00 UTC
[3/6] mesos git commit: Updated the release guide with handy JIRA
queries.
Updated the release guide with handy JIRA queries.
Review: https://reviews.apache.org/r/53429
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/d6fe0636
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/d6fe0636
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/d6fe0636
Branch: refs/heads/master
Commit: d6fe0636dc4fd7c8a225710b82bdcd3b2ffbe20a
Parents: 5c7b9eb
Author: Alexander Rukletsov <al...@apache.org>
Authored: Thu Nov 3 15:02:30 2016 +0100
Committer: Alexander Rukletsov <al...@apache.org>
Committed: Thu Nov 3 22:13:34 2016 +0100
----------------------------------------------------------------------
docs/release-guide.md | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/d6fe0636/docs/release-guide.md
----------------------------------------------------------------------
diff --git a/docs/release-guide.md b/docs/release-guide.md
index 6ced432..ee9b005 100644
--- a/docs/release-guide.md
+++ b/docs/release-guide.md
@@ -62,7 +62,9 @@ This guide describes the process of doing an official release of Mesos.
or `Target Version` as the release version to the next release version.
> PROTIP: Use a JIRA dashboard [(example)](https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329720)
- to track the progress of targeted issues as the release date approaches.
+ 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)`
> 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 spamming.
@@ -76,7 +78,9 @@ This guide describes the process of doing an official release of Mesos.
* Make sure all new API changes, deprecations, major features, and features
graduating from experimental to stable are called out at the top of the
- `CHANGELOG`.
+ `CHANGELOG`. This JIRA query may be helpful in identifying some of these
+ (`<X.Y.Z>` is the release version):
+ `project = MESOS AND "Target Version/s" = <X.Y.Z> AND type = Epic`
* Ensure that the "Unresolved Critical Issues" section is populated
correctly. This JIRA query may be helpful: