svn commit: r674053 - /maven/site/trunk/src/site/apt/developers/conventions/jira.apt

[vs...@apache.org]

Author: vsiveton
Date: Fri Jul  4 06:40:59 2008
New Revision: 674053

URL: http://svn.apache.org/viewvc?rev=674053&view=rev
Log:
o added a section when to create issue in jira

Modified:
    maven/site/trunk/src/site/apt/developers/conventions/jira.apt

Modified: maven/site/trunk/src/site/apt/developers/conventions/jira.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/conventions/jira.apt?rev=674053&r1=674052&r2=674053&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/conventions/jira.apt (original)
+++ maven/site/trunk/src/site/apt/developers/conventions/jira.apt Fri Jul  4 06:40:59 2008
@@ -3,7 +3,7 @@
  ------
  Vincent Siveton
  ------
- 2008-07-03
+ 2008-07-04
  ------
 
 ~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -30,7 +30,21 @@
 
  This document describes how Maven developers should use Jira, our issue tracking.
 
-* Issue Details
+* When To Create a JIRA Issue?
+
+ This section discusses when to create a JIRA issue versus just committing a change in SVN.
+
+ * <<Minor changes>>, like bug fixes, documentation fixes, etc. that aren't going to impact other users can be
+ committed without much issue.
+
+ * <<Larger changes>>, like API changes, significant refactoring, new classes, and pretty much any change of more than
+  100 lines, should have a JIRA ticket associated with it, or at least an email discussion.
+
+ []
+
+* How To Use Issue Details?
+
+ This section presents some conventions about the issue fields.
 
 ** Priority