[hbase] branch branch-2.1 updated: HBASE-19230 Write up fixVersion policy from dev discussion in refguide

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

janh pushed a commit to branch branch-2.1
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/branch-2.1 by this push:
     new 84ee724  HBASE-19230 Write up fixVersion policy from dev discussion in refguide
84ee724 is described below

commit 84ee7244d7dea087ec1e5aec695dc93809188f42
Author: syedmurtazahassan <sy...@gmail.com>
AuthorDate: Sat Jul 13 18:00:44 2019 +0200

    HBASE-19230 Write up fixVersion policy from dev discussion in refguide
    
    Signed-off-by: Jan Hentschel <ja...@ultratendency.com>
---
 src/main/asciidoc/_chapters/developer.adoc | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/src/main/asciidoc/_chapters/developer.adoc b/src/main/asciidoc/_chapters/developer.adoc
index a3c90b1..eda53be 100644
--- a/src/main/asciidoc/_chapters/developer.adoc
+++ b/src/main/asciidoc/_chapters/developer.adoc
@@ -1592,6 +1592,18 @@ We use Git for source code management and latest development happens on `master`
 branches for past major/minor/maintenance releases and important features and bug fixes are often
  back-ported to them.
 
+=== Policy for Fix Version in JIRA
+
+To determine if a given fix is in a given release purely from the release numbers following rules
+are defined:
+
+Fix version of X.Y.Z => fixed in all releases X.Y.Z' (where Z' = Z).
+Fix version of X.Y.0 => fixed in all releases X.Y'.* (where Y' = Y).
+Fix version of X.0.0 => fixed in all releases X'.\*.* (where X' = X).
+
+By this policy, fix version of 1.3.0 implies 1.4.0, but 1.3.2 does not imply 1.4.0 as we could not
+tell purely from the numbers which release came first.
+
 [[code.standards]]
 === Code Standards