Agree. Better not to complicate this introducing the extra. For the early major releases, release notes can be manually written to document the great features; later in minor releases, JIRAs can be referenced.
Regards, Kai -----Original Message----- From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com] Sent: Sunday, April 10, 2016 3:25 AM To: dev@mnemonic.incubator.apache.org Subject: Re: Maintaining CHANGES.txt file for capturing project change log I think Yetus project has a tool to generate release notes from git log itself. I feel adding one entry for every commit in CHANGES.txt this is unnecessary step. In recent days we stopped tracking commit details in CHANGES.txt in Hadoop project as well, thinking this is unnecessary and Yetus can generate. May be until we integrate such tools, we can track CHANGES.txt as temporary solution? This would basically useful for generating Release notes. Regards, Uma From: Rakesh Radhakrishnan <rakeshr.apa...@gmail.com<mailto:rakeshr.apa...@gmail.com>> Reply-To: "dev@mnemonic.incubator.apache.org<mailto:dev@mnemonic.incubator.apache.org>" <dev@mnemonic.incubator.apache.org<mailto:dev@mnemonic.incubator.apache.org>> Date: Saturday, April 9, 2016 at 10:24 AM To: "dev@mnemonic.incubator.apache.org<mailto:dev@mnemonic.incubator.apache.org>" <dev@mnemonic.incubator.apache.org<mailto:dev@mnemonic.incubator.apache.org>> Subject: Maintaining CHANGES.txt file for capturing project change log Hi All, I think we need to maintain CHANGES.txt file to capture the change log details which can be used for a full list of changes in a release. I'm attaching one sample file with this mail. This can be used and fill the change log details while committing next change in the project. Location of this file: master/CHANGES.txt Thanks, Rakesh
