Heya, The CHANGES.md file on branch-2.3 weighs in at over 1mb and is too big for Github to render. Its content covers back to 0.99. This isn't really usable by someone who wants to easily see what's new in the latest patch release.
I propose we truncate these changes files to what's new for the release branch. It probably needs some more work, but the git-jira audit script [0] is able to generate a report of what's new (never previously released) for a target release-line branch. We could use this as the basis for the CHANGES file when starting a new release-line branch. From then on, Yetus takes care of the patch release updates. What do you think? Thanks, Nick [0]: https://github.com/apache/hbase/tree/master/dev-support/git-jira-release-audit
