[
https://issues.apache.org/jira/browse/HBASE-14025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621278#comment-14621278
]
Enis Soztutar commented on HBASE-14025:
---------------------------------------
bq. What about having the committers continue with their current habit and then
leaving it to the release managers to make things consistent around release
time?
bq. There's some homework and burden placed on the RM to be sure. However other
alternatives seem less optimal to me.
Sounds reasonable. RM, at the time of the release, should know about the status
of branches and jiras for the release anyway, so she can do a better job at
this than committers at the commit time.
> 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)
