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.
Target branches: master, 3.5, 3.4. Author: Michael Han <[email protected]> Reviewers: Edward Ribeiro <[email protected]>, Flavio Junqueira <[email protected]>, Rakesh Radhakrishnan <[email protected]> Closes #154 from hanm/ZOOKEEPER-2672 Project: http://git-wip-us.apache.org/repos/asf/zookeeper/repo Commit: http://git-wip-us.apache.org/repos/asf/zookeeper/commit/f35bca0b Tree: http://git-wip-us.apache.org/repos/asf/zookeeper/tree/f35bca0b Diff: http://git-wip-us.apache.org/repos/asf/zookeeper/diff/f35bca0b Branch: refs/heads/master Commit: f35bca0b36c3d5ac0282cc5519fbd372e6632394 Parents: 434abbb Author: Michael Han <[email protected]> Authored: Fri Feb 10 14:17:36 2017 +0530 Committer: Rakesh Radhakrishnan <[email protected]> Committed: Fri Feb 10 14:17:36 2017 +0530 ---------------------------------------------------------------------- CHANGES.txt | 3302 ------------------------------------------------------ 1 file changed, 3302 deletions(-) ----------------------------------------------------------------------
