You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by sr...@apache.org on 2020/02/01 00:33:39 UTC
[spark-website] branch asf-site updated: Add target version of
blockers
This is an automated email from the ASF dual-hosted git repository.
srowen pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 86f060b Add target version of blockers
86f060b is described below
commit 86f060b345abe82ff6ae21600de916c7263e5614
Author: Dongjoon Hyun <dh...@apple.com>
AuthorDate: Fri Jan 31 18:33:24 2020 -0600
Add target version of blockers
Author: Dongjoon Hyun <dh...@apple.com>
Closes #258 from dongjoon-hyun/target.
---
contributing.md | 2 +-
site/contributing.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/contributing.md b/contributing.md
index 9cde6ce..3016a26 100644
--- a/contributing.md
+++ b/contributing.md
@@ -268,7 +268,7 @@ Example: `Fix typos in Foo scaladoc`
Blockers. JIRA tends to unfortunately conflate "size" and "importance" in its
Priority field values. Their meaning is roughly:
1. Blocker: pointless to release without this change as the release would be unusable
- to a large minority of users. Correctness and data loss issues should be considered Blockers.
+ to a large minority of users. Correctness and data loss issues should be considered Blockers for their target versions.
1. Critical: a large minority of users are missing important functionality without
this, and/or a workaround is difficult
1. Major: a small minority of users are missing important functionality without this,
diff --git a/site/contributing.html b/site/contributing.html
index b29d381..98f7ed9 100644
--- a/site/contributing.html
+++ b/site/contributing.html
@@ -488,7 +488,7 @@ Example: <code class="highlighter-rouge">Fix typos in Foo scaladoc</code></li>
Priority field values. Their meaning is roughly:
<ol>
<li>Blocker: pointless to release without this change as the release would be unusable
- to a large minority of users. Correctness and data loss issues should be considered Blockers.</li>
+ to a large minority of users. Correctness and data loss issues should be considered Blockers for their target versions.</li>
<li>Critical: a large minority of users are missing important functionality without
this, and/or a workaround is difficult</li>
<li>Major: a small minority of users are missing important functionality without this,
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org