[10/22] incubator-tinkerpop git commit: Modifications to issue conventions in README.

[sp...@apache.org]

Modifications to issue conventions in README.


Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/3b8cba01
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/3b8cba01
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/3b8cba01

Branch: refs/heads/variables
Commit: 3b8cba01b9f9f1e1a9e6739e7f52a6e48ba448ae
Parents: 1b37172
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Fri Mar 27 09:59:36 2015 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Fri Mar 27 09:59:36 2015 -0400

----------------------------------------------------------------------
 README.asciidoc | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/3b8cba01/README.asciidoc
----------------------------------------------------------------------
diff --git a/README.asciidoc b/README.asciidoc
index 89d64c5..b98207e 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -98,7 +98,6 @@ TinkerPop3 uses Apache JIRA as its link:https://issues.apache.org/jira/browse/TI
 * An issue's "status" should be in one of two states: `open` or `closed`.
 ** An `open` issue is newly created, under consideration or otherwise in progress.
 ** A `closed` issue is completed for purposes of release (i.e. code, testing, and documentation complete).
-* When marking an issue as `closed`, its "resolution" field should always be set to `done`.  This single resolution simply means that the issue is complete, purposely does not convey the manner in which it was completed.  Consult the comments for information on the circumstances representing how the issue was resolved.  Taking this approach gives "resolution" only two status: `unresolved` and `done`.
 * An issue's "type" should be one of two options: `bug` or `improvement`.  A `bug` has a very specific meaning, referring to an error that prevents usage of TinkerPop AND does not have a reasonable workaround.  Given that definition, a `bug` should generally have very high priority for a fix.  Everything else is an `improvement` in the sense that any other work is an enhancement to the current codebase.
 * The "component" should be representative of the primary area of code that it applies to and all issues should have this property set.
 * The "priority" of an issue is represented by two states `critical` and `major`.  It should be assigned as follows: