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:
parent
8defea9561
commit
c5f879483d
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in New Issue