From c5f879483d71e53ea65f0609fc7905ef71b34e82 Mon Sep 17 00:00:00 2001 From: syedmurtazahassan Date: Sat, 13 Jul 2019 18:00:44 +0200 Subject: [PATCH] HBASE-19230 Write up fixVersion policy from dev discussion in refguide Signed-off-by: Jan Hentschel --- 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 3c02fe50bd7..1d3dd0a4cc6 100644 --- a/src/main/asciidoc/_chapters/developer.adoc +++ b/src/main/asciidoc/_chapters/developer.adoc @@ -1783,6 +1783,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