From be885f8ddde8fe60e60b86d2304a7258404d055f Mon Sep 17 00:00:00 2001
From: Michael Stack <stack@apache.org>
Date: Sat, 6 Apr 2013 05:50:22 +0000
Subject: [PATCH] Add what we decided about how to set versions in JIRA when
 resolving an issue

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1465194 13f79535-47bb-0310-9956-ffa450edef68
---
 hbase-assembly/src/docbkx/community.xml | 35 ++++++++++++++++++++-----
 1 file changed, 29 insertions(+), 6 deletions(-)

diff --git a/hbase-assembly/src/docbkx/community.xml b/hbase-assembly/src/docbkx/community.xml
index 2c09908aed9..075f5346908 100644
--- a/hbase-assembly/src/docbkx/community.xml
+++ b/hbase-assembly/src/docbkx/community.xml
@@ -36,7 +36,7 @@
         keep elsewhere -- it should be public so it can be observed -- and you can update dev mailing list on progress.   When the feature is ready for commit,
         3 +1s from committers will get your feature merged<footnote><para>See <link xlink:href="http://search-hadoop.com/m/asM982C5FkS1">HBase, mail # dev - Thoughts about large feature dev branches</link></para></footnote>
         </para>
-      </section>         
+      </section>
       <section xml:id="patchplusonepolicy">
         <title>Patch +1 Policy</title>
         <para>
@@ -47,7 +47,7 @@ first to see if it works before we cast it in stone.
 <para>
 Apache HBase is made of
 <link xlink:href="https://issues.apache.org/jira/browse/HBASE#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel">components</link>.
-Components have one or more <xref linkend="OWNER" />s.  See the 'Description' field on the 
+Components have one or more <xref linkend="OWNER" />s.  See the 'Description' field on the
 <link xlink:href="https://issues.apache.org/jira/browse/HBASE#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel">components</link>
 JIRA page for who the current owners are by component.
 </para>
@@ -67,8 +67,31 @@ first pass).
 Any -1 on a patch by anyone vetos a patch; it cannot be committed
 until the justification for the -1 is addressed.
 </para>
-      </section>         
-    </section>    
+      </section>
+      <section xml:id="hbase.fix.version.in.JIRA">
+          <title>How to set fix version in JIRA on issue resolve</title>
+          <para>Here is how <link xlink:href="http://search-hadoop.com/m/azemIi5RCJ1">we agreed</link> to set versions in JIRA when we
+              resolve an issue.  If trunk is going to be 0.98.0 then:
+              <itemizedlist>
+                  <listitem><para>
+              Commit only to trunk: Mark with 0.98
+                </para></listitem>
+                  <listitem><para>
+              Commit to 0.95 and trunk : Mark with 0.98, and 0.95.x
+                </para></listitem>
+                  <listitem><para>
+              Commit to 0.94.x and 0.95, and trunk: Mark with 0.98, 0.95.x, and 0.94.x
+                </para></listitem>
+                  <listitem><para>
+              Commit to 89-fb: Mark with 89-fb.
+                </para></listitem>
+                  <listitem><para>
+              Commit site fixes: no version
+                </para></listitem>
+          </itemizedlist>
+          </para>
+      </section>
+    </section>
     <section xml:id="community.roles">
       <title>Community Roles</title>
       <section xml:id="OWNER">
@@ -104,6 +127,6 @@ goals or the design toward which they are driving their component
 If you would like to be volunteer as a component owner, just write the
 dev list and we'll sign you up. Owners do not need to be committers.
 </para>
-      </section>         
-    </section>    
+      </section>
+    </section>
     </chapter>