You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ni...@apache.org on 2015/10/29 18:39:15 UTC
[1/3] cordova-coho git commit: Adding docs around JIRA issue triage
Repository: cordova-coho
Updated Branches:
refs/heads/master 5605fa1c3 -> 9a736a3e4
Adding docs around JIRA issue triage
Project: http://git-wip-us.apache.org/repos/asf/cordova-coho/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/37cd2fe5
Tree: http://git-wip-us.apache.org/repos/asf/cordova-coho/tree/37cd2fe5
Diff: http://git-wip-us.apache.org/repos/asf/cordova-coho/diff/37cd2fe5
Branch: refs/heads/master
Commit: 37cd2fe5548e3ad9cdb0908135084efba5006cae
Parents: 5605fa1
Author: Nikhil Khandelwal <ni...@microsoft.com>
Authored: Tue Oct 20 08:53:02 2015 -0700
Committer: Nikhil Khandelwal <ni...@microsoft.com>
Committed: Tue Oct 27 18:02:21 2015 -0700
----------------------------------------------------------------------
docs/index.md | 1 +
docs/jira-triage.md | 34 ++++++++++++++++++++++++++++++++++
2 files changed, 35 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/37cd2fe5/docs/index.md
----------------------------------------------------------------------
diff --git a/docs/index.md b/docs/index.md
index e197bd9..b17502a 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -14,6 +14,7 @@
* [Committer workflow](committer-workflow.md)
* [Code Reviews](code-reviews.md)
* [Processing Pull Requests](processing-pull-requests.md)
+* [Triaging JIRAS](jira-triage.md)
## Misc
* [Doc translation Process](doc-translation-process.md)
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/37cd2fe5/docs/jira-triage.md
----------------------------------------------------------------------
diff --git a/docs/jira-triage.md b/docs/jira-triage.md
new file mode 100644
index 0000000..6fad6ff
--- /dev/null
+++ b/docs/jira-triage.md
@@ -0,0 +1,34 @@
+#JIRA Issue Triage Process
+
+##Goal
+Every issue needs to be triaged. A triaged issue is actionable and there is an eventual desire to resolve it and has all the fields set accurately. In particular, low quality issues and eliminated from the system. Also, critical issues need to be fixed asap and this process should highlight those.
+
+##Process
+Go through each [unresolved bug that is not labeled 'triaged' ordered by created Date](https://issues.apache.org/jira/issues/?jql=status%20not%20in%20(Resolved%2C%20Closed)%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20triaged)%20AND%20%20project%20%3D%20CB%20ORDER%20BY%20createdDate%20DESC).
+
+- Ensure the bug details has sufficient details for a repro. If not, message the reporter with questions. If the reporter does not respond in 2 business days. Resolve the bug as `Invalid`.
+- If you can reproduce the issue. Add a label `reproduced`. If not, Resolve the bug as `Cannot reproduce`.
+- If you are not an expert in the area or do not have the hardware for triaging, reference the component owner in helping triage the bug.
+- Edit the following fields:
+ - **Component**: Should be ideally a single component. *For plugin issues do not add platform names here.*
+ - **Work item type**: Ensure it has the correct classification - feature request vs task vs bug.
+ - **Priority**:
+ - `Blocker`: This will block the current release of the component.
+ - `Critical`: This will cause the main function of the component to fail and needs to be fixed asap.
+ - `Major`: Important one to fix.
+ - `Minor`, `Trivial`: Nice to haves.
+ - **Label**: Use the following:
+ - `regression` - A change introduced in previous release or commit that surfaced the issue. Ideally, add a link to the commit that caused the issue.
+ - `ios`, `android`, `windows` etc. platforms - If it is a plugin issue and affects one of these platforms
+ - `easyfix` - For issues that are easy for a new contributor to fix. We will eventually publish an easyfix query for new contributors to participate.
+ - `triaged` - Indicates bug that has been triaged and does not need to be triaged again.
+ - `reproduced` - Bug that has a reproduction.
+ - **Environment**: Represents the machine setup required to reproduce the problem. Great place for mobile OS, host OS versions etc.
+ - **Affected version**: Specify the version of the component that the issue appears in.
+
+At the end of triage session, send an e-mail to the dev list discussing bugs that need urgent attention. Good bugs in this area are recent regressions or other issues having a wide impact. These would require a patch release to fix them.
+
+##Open issues
+- Assignments: Who does JIRA triage? Do we need a weekly rotation duty? Should we publish a schedule? Should we distribute by component?
+- Auto-assignments: Currently JIRA has auto-assignments based on component owner. Does that still make sense?
+
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[2/3] cordova-coho git commit: Made some tweaks based on feedback
Posted by ni...@apache.org.
Made some tweaks based on feedback
Project: http://git-wip-us.apache.org/repos/asf/cordova-coho/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/47f564f9
Tree: http://git-wip-us.apache.org/repos/asf/cordova-coho/tree/47f564f9
Diff: http://git-wip-us.apache.org/repos/asf/cordova-coho/diff/47f564f9
Branch: refs/heads/master
Commit: 47f564f9e0dcc3b256b2cd5bbdf78208adc181f5
Parents: 37cd2fe
Author: Nikhil Khandelwal <ni...@microsoft.com>
Authored: Fri Oct 23 17:07:10 2015 -0700
Committer: Nikhil Khandelwal <ni...@microsoft.com>
Committed: Tue Oct 27 18:02:22 2015 -0700
----------------------------------------------------------------------
docs/jira-triage.md | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/47f564f9/docs/jira-triage.md
----------------------------------------------------------------------
diff --git a/docs/jira-triage.md b/docs/jira-triage.md
index 6fad6ff..6360f0f 100644
--- a/docs/jira-triage.md
+++ b/docs/jira-triage.md
@@ -1,20 +1,20 @@
#JIRA Issue Triage Process
##Goal
-Every issue needs to be triaged. A triaged issue is actionable and there is an eventual desire to resolve it and has all the fields set accurately. In particular, low quality issues and eliminated from the system. Also, critical issues need to be fixed asap and this process should highlight those.
+Every issue needs to be triaged. A triaged issue is actionable and there is an eventual desire to resolve it and has all the fields set accurately. In particular, low quality issues are eliminated from the system. Also, critical issues need to be fixed asap and this process should highlight those.
##Process
Go through each [unresolved bug that is not labeled 'triaged' ordered by created Date](https://issues.apache.org/jira/issues/?jql=status%20not%20in%20(Resolved%2C%20Closed)%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20triaged)%20AND%20%20project%20%3D%20CB%20ORDER%20BY%20createdDate%20DESC).
-- Ensure the bug details has sufficient details for a repro. If not, message the reporter with questions. If the reporter does not respond in 2 business days. Resolve the bug as `Invalid`.
+- Ensure the bug details has sufficient details for a repro. If not, message the reporter with questions. If the reporter does not respond in 4 business days. Resolve the bug as `Invalid`. They are welcome to re-activate the bug with details at a later date.
- If you can reproduce the issue. Add a label `reproduced`. If not, Resolve the bug as `Cannot reproduce`.
-- If you are not an expert in the area or do not have the hardware for triaging, reference the component owner in helping triage the bug.
+- If you are not an expert in the area or do not have the hardware for triaging, reference the platform and/or component owner in helping triage the bug.
- Edit the following fields:
- **Component**: Should be ideally a single component. *For plugin issues do not add platform names here.*
- **Work item type**: Ensure it has the correct classification - feature request vs task vs bug.
- **Priority**:
- - `Blocker`: This will block the current release of the component.
- - `Critical`: This will cause the main function of the component to fail and needs to be fixed asap.
+ - `Blocker`: This will block the current release of the component. The failure is catastrpphic and easy to hit. 'Hello world' and [mobilespec](https://github.com/apache/cordova-mobile-spec) does not build or crashes.
+ - `Critical`: This will cause the main function of the component to fail and needs to be fixed asap but will not block the release.
- `Major`: Important one to fix.
- `Minor`, `Trivial`: Nice to haves.
- **Label**: Use the following:
@@ -28,6 +28,12 @@ Go through each [unresolved bug that is not labeled 'triaged' ordered by created
At the end of triage session, send an e-mail to the dev list discussing bugs that need urgent attention. Good bugs in this area are recent regressions or other issues having a wide impact. These would require a patch release to fix them.
+##Asking for help
+Sometimes while there is a bug or a feature request that seems valid, but it might not be high priority for one of the committers to fix. Following up with the issue reporter quickly and coaching him thorugh making a contribution with a pull request is a good idea.
+
+##Dealing with feature requests
+New features to plugins should ideally be cross platform (at least across more than one major platform - Android, iOS, Windows). The design should account for ease of detection or meaningful degradation in the absence of the feature on a partcular platform. For feature requests that are overly specific to a particular usecase - we should resolve them with resolution reason `Later` or `Won't Fix`. There is little value in carrying the debt of these issues.
+
##Open issues
- Assignments: Who does JIRA triage? Do we need a weekly rotation duty? Should we publish a schedule? Should we distribute by component?
- Auto-assignments: Currently JIRA has auto-assignments based on component owner. Does that still make sense?
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[3/3] cordova-coho git commit: Update jira-triage.md
Posted by ni...@apache.org.
Update jira-triage.md
- Added more details around assignment.
- Fixed the typo that Shaz pointed out. Merging this in now.. This closes #97
Project: http://git-wip-us.apache.org/repos/asf/cordova-coho/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/9a736a3e
Tree: http://git-wip-us.apache.org/repos/asf/cordova-coho/tree/9a736a3e
Diff: http://git-wip-us.apache.org/repos/asf/cordova-coho/diff/9a736a3e
Branch: refs/heads/master
Commit: 9a736a3e44300561491f972a2528ea8edfe4768c
Parents: 47f564f
Author: Nikhil Khandelwal <ni...@microsoft.com>
Authored: Tue Oct 27 17:21:29 2015 -0700
Committer: Nikhil Khandelwal <ni...@microsoft.com>
Committed: Tue Oct 27 18:02:24 2015 -0700
----------------------------------------------------------------------
docs/jira-triage.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/9a736a3e/docs/jira-triage.md
----------------------------------------------------------------------
diff --git a/docs/jira-triage.md b/docs/jira-triage.md
index 6360f0f..9975b0c 100644
--- a/docs/jira-triage.md
+++ b/docs/jira-triage.md
@@ -13,7 +13,7 @@ Go through each [unresolved bug that is not labeled 'triaged' ordered by created
- **Component**: Should be ideally a single component. *For plugin issues do not add platform names here.*
- **Work item type**: Ensure it has the correct classification - feature request vs task vs bug.
- **Priority**:
- - `Blocker`: This will block the current release of the component. The failure is catastrpphic and easy to hit. 'Hello world' and [mobilespec](https://github.com/apache/cordova-mobile-spec) does not build or crashes.
+ - `Blocker`: This will block the current release of the component. The failure is catastrophic and easy to hit. 'Hello world' and [mobilespec](https://github.com/apache/cordova-mobile-spec) does not build or crashes.
- `Critical`: This will cause the main function of the component to fail and needs to be fixed asap but will not block the release.
- `Major`: Important one to fix.
- `Minor`, `Trivial`: Nice to haves.
@@ -25,6 +25,7 @@ Go through each [unresolved bug that is not labeled 'triaged' ordered by created
- `reproduced` - Bug that has a reproduction.
- **Environment**: Represents the machine setup required to reproduce the problem. Great place for mobile OS, host OS versions etc.
- **Affected version**: Specify the version of the component that the issue appears in.
+ - **Assigned To**: If you plan to work on a particular issue, assign it to yourself. If the issue has not been worked on by the assignee i.e. status is not `in progress` or it's clear that the assignee is not looking at this actively. The issue can be taken up by anyone.
At the end of triage session, send an e-mail to the dev list discussing bugs that need urgent attention. Good bugs in this area are recent regressions or other issues having a wide impact. These would require a patch release to fix them.
@@ -36,5 +37,3 @@ New features to plugins should ideally be cross platform (at least across more t
##Open issues
- Assignments: Who does JIRA triage? Do we need a weekly rotation duty? Should we publish a schedule? Should we distribute by component?
-- Auto-assignments: Currently JIRA has auto-assignments based on component owner. Does that still make sense?
-
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org