[
https://issues.apache.org/jira/browse/HBASE-14025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628248#comment-14628248
]
Lars Hofhansl commented on HBASE-14025:
---------------------------------------
I find this still confusing (or not right). If we do not follow branches in
jira some things are getting quite complicated:
* if (say) 1.2.0 was not released, yet, but 1.2 was already branched the
committer has to remember that when committing to branch-1 which will be (say)
1.3.0
* one cannot just copy the (again, say) CHANGES.txt from 1.2.0 (once it's
released) into 1.3.0 and fill in the 1.3.0 changes from jira. If jira is the
source of truth that should be possible
* I'd still want to see 1.2.0 changes, followed by the new 1.3.x changes, no?
* since we branch 1.2 before 1.2.0 is released (and hence branch-1 becomes
1.3.0) we can simply copy the CHANGES.txt from 1.2.0 and fill in the 1.3.x
changes, instead.
So I still find it cleaner to set "Fix Version/s" to all affected branches/tags.
> Update CHANGES.txt for 1.2
> --------------------------
>
> Key: HBASE-14025
> URL: https://issues.apache.org/jira/browse/HBASE-14025
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 1.2.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Fix For: 1.2.0
>
>
> Since it's more effort than I expected, making a ticket to track actually
> updating CHANGES.txt so that new RMs have an idea what to expect.
> Maybe will make doc changes if there's enough here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
