[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395922#comment-14395922
]
Tsz Wo Nicholas Sze commented on HADOOP-11731:
----------------------------------------------
Why don't we use the git commit message instead of JIRA summary? The git
commit message is supposed to be the same as the entry in CHAGNES.txt.
BTW, I guess the tool won't handle the case that there are multiple
contributors if it takes JIRA assignee as the contributor. We should also
retrieve the contributor list from the commit message.
> ... Any effort put into updating those files is wasted effort given that it's
> automated now.
I disagree since the automation may have bugs or may not work at all.
> 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)
