[
https://issues.apache.org/jira/browse/ZOOKEEPER-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860621#comment-15860621
]
Rakesh R commented on ZOOKEEPER-2672:
-------------------------------------
Thanks [~hanm] for the fix and others for the helpful comments.
Committed to branch-3.4:
https://git-wip-us.apache.org/repos/asf?p=zookeeper.git;a=commit;h=286bf6913f3eed1ea9ee3e3523b2e8b6bdea56ba
Committed to branch-3.5:
https://git-wip-us.apache.org/repos/asf?p=zookeeper.git;a=commit;h=4bc78ee81c50bbbaed0b29c0c15a4b58b6599b32
Committed to master:
https://git-wip-us.apache.org/repos/asf?p=zookeeper.git;a=commit;h=f35bca0b36c3d5ac0282cc5519fbd372e6632394
> Remove CHANGE.txt
> -----------------
>
> Key: ZOOKEEPER-2672
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2672
> Project: ZooKeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.4.9, 3.5.2
> Reporter: Michael Han
> Assignee: Michael Han
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> The CHANGE.txt is already not the source of truth of what's changed after we
> migrating to git - most of the git commits in recent couple of months don't
> update CHANGE.txt. The option of updating CHANGE.txt during commit flow
> automatically is none trivial, and do that manually is cumbersome and error
> prone.
> The consensus is we would rely on source control revision logs instead of
> CHANGE.txt moving forward; see
> https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html for more
> details.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
