ZOOKEEPER-2672: Remove CHANGE.txt 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/devzookeeper.apache.org/msg37108.html for more details.
Author: Michael Han <[email protected]> Reviewers: Edward Ribeiro <[email protected]>, Flavio Junqueira <[email protected]>, Rakesh Radhakrishnan <[email protected]> Closes #168 from hanm/ZOOKEEPER-2672-branch-3.4 Project: http://git-wip-us.apache.org/repos/asf/zookeeper/repo Commit: http://git-wip-us.apache.org/repos/asf/zookeeper/commit/286bf691 Tree: http://git-wip-us.apache.org/repos/asf/zookeeper/tree/286bf691 Diff: http://git-wip-us.apache.org/repos/asf/zookeeper/diff/286bf691 Branch: refs/heads/branch-3.4 Commit: 286bf6913f3eed1ea9ee3e3523b2e8b6bdea56ba Parents: 053a9d2 Author: Michael Han <[email protected]> Authored: Fri Feb 10 14:25:30 2017 +0530 Committer: Rakesh Radhakrishnan <[email protected]> Committed: Fri Feb 10 14:25:30 2017 +0530 ---------------------------------------------------------------------- CHANGES.txt | 2616 ------------------------------------------------------ 1 file changed, 2616 deletions(-) ----------------------------------------------------------------------
