Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-19230 Write up fixVersion policy from dev discussion in refguide 

Signed-off-by: Jan Hentschel <jan.hentschel@ultratendency.com>
This commit is contained in:
syedmurtazahassan 2019-07-13 18:00:44 +02:00 committed by Jan Hentschel
parent d26e9d04e1
commit 84ee7244d7
No known key found for this signature in database
GPG Key ID: 5CD818B19CC299A3
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/main/asciidoc/_chapters/developer.adoc
View File

@ -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 branches for past major/minor/maintenance releases and important features and bug fixes are often
back-ported to them. 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]]
=== Code Standards === Code Standards