Hi, I found that changing CHANGES.txt when committing a jira is error prone because of the different sections in the file, and sometimes we forget about changing this file.
After all, git log would indicate the history of a branch. I wonder if we could switch to a new method: 1. When committing, ensure the message include the type of the jira, "New Feature", "Bug Fixes", "Improvement" etc. 2. No longer need to make changes to CHANGES.txt for each commit 3. Before releasing a branch, create the CHANGES.txt by using "git log" command for the given branch.. Thanks. --Yongjun
