[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393572#comment-14393572
]
Allen Wittenauer commented on HADOOP-11731:
-------------------------------------------
bq. Have you compared the current CHANGES.txt with the generated change log? I
beg the diff is long.
The summary lines no. The content that matters? Very much so. I spent about a
man month repairing fix version information for all of branch-2 and trunk. To
the point that I know that this statement is patently false:
bq. However, it worked well in the past for many releases.
I'd argue it has failed tremendously in past releases.
* the number of incompatible changes that have been committed as bug fixes or
what not with zero release notes to warn the user that we've screwed them over.
* CHANGES.txt is missing *hundreds* of commits in both branch-2 and trunk. The
number of JIRAs that needed to have 2.7.0 added to the fixversion vs.
autogenerated was _3_.
* Right now, branch-2 and 2.7.0 changes.txt files even disagree about what
patches are in 2.7.0. That's not success at all.
The concern about the summary line is sort of moot since:
a) the reverse is also true: it's rare that the changes.txt gets updated when
it's incorrect vs the jira summary
b) the generated results provide links to the jira, providing easy click
history to see what has happened.
> 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)
