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

[vs...@apache.org]

Author: vsiveton
Date: Sat Jul  5 06:14:18 2008
New Revision: 674194

URL: http://svn.apache.org/viewvc?rev=674194&view=rev
Log:
o improved doc due to comments on dev@

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=674194&r1=674193&r2=674194&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/conventions/jira.apt (original)
+++ maven/site/trunk/src/site/apt/developers/conventions/jira.apt Sat Jul  5 06:14:18 2008
@@ -3,7 +3,7 @@
  ------
  Vincent Siveton
  ------
- 2008-07-04
+ 2008-07-05
  ------
 
 ~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -34,11 +34,11 @@
 
  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.
+ * <<Minor changes>>, like code reformatting, 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.
+ * <<Larger changes>>, like bug fixes, 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.
 
  []
 
@@ -89,4 +89,6 @@
 
  * {{{http://www.atlassian.com/software/jira/docs/latest/projects.html}What is a project?}}
 
+ * {{{http://markmail.org/message/wfv2lw66i2gggnaq}how we handle JIRA versions Thread}}
+
  []