You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by sp...@apache.org on 2015/08/10 20:26:49 UTC
[08/14] incubator-tinkerpop git commit: Mention the breaking label
for jira in release notes.
Mention the breaking label for jira in release notes.
Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/dec75e5c
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/dec75e5c
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/dec75e5c
Branch: refs/heads/master
Commit: dec75e5c36640530d4440851d7fcd2d6bdd58437
Parents: 005c0e5
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Mon Aug 10 06:52:41 2015 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Mon Aug 10 06:52:41 2015 -0400
----------------------------------------------------------------------
README.asciidoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/dec75e5c/README.asciidoc
----------------------------------------------------------------------
diff --git a/README.asciidoc b/README.asciidoc
index 86b7f33..7f1b6e7 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -98,7 +98,7 @@ TinkerPop3 uses Apache JIRA as its link:https://issues.apache.org/jira/browse/TI
** 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.
-* Issues are not assigned "labels".
+* Issues are not assigned "labels" with one exception: the "breaking" label. The "breaking" label marks an issue as one that is representative of a change in the API that might affect users or vendors. This label is important when organizing release notes.
* The "affects/fix version(s)" fields should be appropriately set, where the "fix version" implies the version on which that particular issue will completed.
Release Process