Thanks your responses! Seems like all of you prefer to have both trivial
and non-trivial updates in CHANGES.txt. I'm going to keep that in mind,
but will continue to omit them for documentation edits.


On 18.07.2017 23:49, kurt greaves wrote:
> I agree that all patches should be added to changes.txt, just to rule out
> any ambiguities. When people look at Changes.txt it's usually to find
> something specific, not to browse the list of changes. Anything significant
> should make it into news.txt, which is more appropriate for users.
> changes.txt is more aimed at developers in my opinion.
> 
> On that note, messages like "Remove unused method" should be more specific,
> that's just a bad commit message in general, and doesn't give at context.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to