Skip to content

Commit

Permalink
HBASE-19230 Write up fixVersion policy from dev discussion in refguide
Browse files Browse the repository at this point in the history
Signed-off-by: Jan Hentschel <[email protected]>
  • Loading branch information
murtazahassan123 authored and HorizonNet committed Jul 13, 2019
1 parent d26e9d0 commit 84ee724
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions src/main/asciidoc/_chapters/developer.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 84ee724

Please sign in to comment.