Skip to content

Commit 84ee724

Browse files
murtazahassan123HorizonNet
authored andcommitted
HBASE-19230 Write up fixVersion policy from dev discussion in refguide
Signed-off-by: Jan Hentschel <jan.hentschel@ultratendency.com>
1 parent d26e9d0 commit 84ee724

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

src/main/asciidoc/_chapters/developer.adoc

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1592,6 +1592,18 @@ We use Git for source code management and latest development happens on `master`
15921592
branches for past major/minor/maintenance releases and important features and bug fixes are often
15931593
back-ported to them.
15941594

1595+
=== Policy for Fix Version in JIRA
1596+
1597+
To determine if a given fix is in a given release purely from the release numbers following rules
1598+
are defined:
1599+
1600+
Fix version of X.Y.Z => fixed in all releases X.Y.Z' (where Z' = Z).
1601+
Fix version of X.Y.0 => fixed in all releases X.Y'.* (where Y' = Y).
1602+
Fix version of X.0.0 => fixed in all releases X'.\*.* (where X' = X).
1603+
1604+
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
1605+
tell purely from the numbers which release came first.
1606+
15951607
[[code.standards]]
15961608
=== Code Standards
15971609

0 commit comments

Comments
 (0)