[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394081#comment-14394081
]
Chris Douglas commented on HADOOP-11731:
----------------------------------------
bq. An example of JIRA information being inaccurate is that the assignee is
missing...
Some of these inconsistencies are easier to spot with the tool, and fix both
JIRA and the release notes. [~aw], would it be difficult to add a report for
cases where the assignee is missing, incompatible changes don't have release
notes, etc? I see it prints a warning for the latter, but a lint-style report
could help RMs fixup JIRA as part of rolling a release.
bq. The single line summary at the top of a JIRA isn't what you are putting in
CHANGES.txt?
I sometimes add more detail in the commit message, but if committers get used
to setting the summary and release notes this seems workable.
> 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
> Assignee: 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)
