Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 2 commits into from
Jul 13, 2019
Merged

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

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
69bc522
HBASE-19230 Write up fixVersion policy from dev discussion in refguide
murtazahassan123 Jul 9, 2019
88c88c3
HBASE-19230 Addressed comments made by Jan
murtazahassan123 Jul 11, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions src/main/asciidoc/_chapters/developer.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down