[
https://issues.apache.org/jira/browse/ZOOKEEPER-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855372#comment-15855372
]
Rakesh R commented on ZOOKEEPER-2672:
-------------------------------------
bq. Rakesh R and Michael Han, Even though I am leaning towards removing the
file too, I think at least one voting round on dev@ or user@ before removing
CHANGE.txt would be nice.
[~eribeiro], I have sent couple of mails about this. Please refer [zk user
mailing list discussion
thread|http://zookeeper-user.578899.n2.nabble.com/Re-CHANGES-txt-td7582909.html]
I believe, this jira needs to be concluded(to avoid confusions - after the
migration to git CHANGE.txt is not the source of truth) before cutting 3.4.10
release. I'm planning to remove CHANGE.txt file in 2 days time frame, 8
February 2017, 6:00 PM (PST), if there is no objection. Thanks!
> 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)
