I have used the CHANGES file in the past, but lately I use Jira. We should take the Jira release notes and dump them into CHANGES when there is a release. git log, while more complete, will have multiple log lines for a ticket.
-Bryan > On May 28, 2015, at 9:09 AM, Phil Sorber <sor...@apache.org > <mailto:sor...@apache.org>> wrote: > > There was some discussion in IRC about removing the CHANGES file. It is > generally disliked and we have JIRA release notes that serve a similar > purpose. Here is an example of JIRA release notes for 6.0.0: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310963&version=12324897 > > <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310963&version=12324897> > > We also have `git log` which can be displayed in a way decent enough to > stand in for the CHANGES file. > > It was pointed out that we should still include something in the tarballs > that had the list of changes for posterity in case JIRA or git history is > ever lost. It was then proposed that we simply add a step to `make rel` > that will take the git shortlog and include it in a file called CHANGES > that only exists in the tarballs. Here is an open JIRA issue for that > effort: > > https://issues.apache.org/jira/browse/TS-3644 > > How does everyone feel about this idea? Is anyone out there using the > CHANGES file?
