syedmurtazahassan commented on a change in pull request #370: HBASE-19230 Write up fixVersion policy from dev discussion in refguide URL: https://github.com/apache/hbase/pull/370#discussion_r302463178
########## File path: src/main/asciidoc/_chapters/developer.adoc ########## @@ -1783,6 +1783,25 @@ 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 + +Currently branch-1 points to branch-1.5 as the upcoming HBase 1.x release. The policy for Fix +Version in Jira is defined below. + +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. + +Also, branch-1 and branch-1.4 have diverged so a fix in one does not necessarily mean a fix is in Review comment: Thanks. Added a new commit addressing your comments. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
