[ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393963#comment-14393963 ]
Tsz Wo Nicholas Sze commented on HADOOP-11731: ---------------------------------------------- > ... the changes.txt gets updated when it's incorrect vs the jira summary We won't update it since CHANGES.txt and jira summary are not supposed to be the same. > the generated results provide links to the jira, providing easy click history > to see what has happened. The entry in CHANGES.txt is a concise statement about the change committed. It takes much more time to understand what was going to read the JIRA itself, especially, when there was a long discussion. > Rework the changelog and releasenotes > ------------------------------------- > > Key: HADOOP-11731 > URL: https://issues.apache.org/jira/browse/HADOOP-11731 > Project: Hadoop Common > Issue Type: New Feature > Components: documentation > Affects Versions: 3.0.0 > Reporter: Allen Wittenauer > Fix For: 3.0.0 > > Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch, > HADOOP-11731-03.patch, HADOOP-11731-04.patch, HADOOP-11731-05.patch, > HADOOP-11731-06.patch, HADOOP-11731-07.patch > > > The current way we generate these build artifacts is awful. Plus they are > ugly and, in the case of release notes, very hard to pick out what is > important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)