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 #169 from hanm/ZOOKEEPER-2672-branch-3.5 Project: http://git-wip-us.apache.org/repos/asf/zookeeper/repo Commit: http://git-wip-us.apache.org/repos/asf/zookeeper/commit/4bc78ee8 Tree: http://git-wip-us.apache.org/repos/asf/zookeeper/tree/4bc78ee8 Diff: http://git-wip-us.apache.org/repos/asf/zookeeper/diff/4bc78ee8 Branch: refs/heads/branch-3.5 Commit: 4bc78ee81c50bbbaed0b29c0c15a4b58b6599b32 Parents: ac864f5 Author: Michael Han <[email protected]> Authored: Fri Feb 10 14:23:33 2017 +0530 Committer: Rakesh Radhakrishnan <[email protected]> Committed: Fri Feb 10 14:23:33 2017 +0530 ---------------------------------------------------------------------- CHANGES.txt | 3297 ------------------------------------------------------ 1 file changed, 3297 deletions(-) ----------------------------------------------------------------------
