[
https://issues.apache.org/jira/browse/HBASE-15347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600230#comment-15600230
]
Mikhail Antonov commented on HBASE-15347:
-----------------------------------------
[~busbey] yeah, I followed the discussion on the linked jira for CHANGES.txt
for 1.2, and the consensus there seems to be that
- we generally choose to make things easier / more obvious for committers at
the cost of possibly a bit more work on RMs side
- as such, fixVersions are set according to which branches the commit goes in
at the time when the jira is resolved
- during RC preparation, RM filters out jiras that marked for both 1.2.0 and
1.3.0 (or any other 2 consecutive minor x.x.0 releases).
Makes sense to me, I'm going to proceed with that.
> Update CHANGES.txt for 1.3
> --------------------------
>
> Key: HBASE-15347
> URL: https://issues.apache.org/jira/browse/HBASE-15347
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 1.3.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Fix For: 1.3.0
>
> Attachments: HBASE-15347-branch-1.3.v1.patch
>
>
> Going to post the steps in preparing changes file for 1.3 here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
