> > +1 for ditching CHANGES.txt. > > I reached out to Allen recently. He wanted to clean up his scripts more > before dropping CHANGES.txt altogether. Should we target 2.8 for this?
I read through our previous threads on this topic, and Allen had some compatibility concerns about dropping CHANGES.txt in a branch-2 release. Allen, do you still have these concerns? You mentioned having written scripts to parse CHANGES.txt. I've written scripts for similar tasks, but what I turned to were git log and JIRA, not CHANGES.txt. I was wondering if this is a relic from the SVN days, since svn log was dog slow. Git log is quite a bit better. My inclination is to just drop CHANGES.txt entirely, including in branch-2. We already have release notes, JIRA, as well as the per-release webpage which talks up the new features. CHANGES.txt also has never been a reliable source of information, and I doubt it has many consumers (if any). Best, Andrew
