[
https://issues.apache.org/jira/browse/ZOOKEEPER-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839537#comment-15839537
]
Flavio Junqueira commented on ZOOKEEPER-2672:
---------------------------------------------
I'm not aware on any dependency on CHANGES.txt, so I'm +1 for removing it.
According to the project bylaws, I'd say that this change corresponds to a
change to the code base, and as such, the vote is by lazy approval, switching
to lazy majority in the case of at least one -1, where the binding votes are
from active committers.
> 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
>
> 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/[email protected]/msg37108.html for more
> details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
