[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387339#comment-14387339
]
Colin Patrick McCabe commented on HADOOP-11731:
-----------------------------------------------
Thanks, Allen. This looks good.
bq. Nope, otherwise releasedocmaker.py --version trunk-win would fail.
OK. I guess we can revisit this later if it becomes an issue. Do you think it
would be helpful to have a log message about the versions that can't be parsed?
Did you confirm that the CHANGES.txt generated for 2.7 is the same as the
current one in branch-2.7? +1 once that is confirmed
We may have to fiddle with some things in JIRA if anything was incorrectly
resolved (with the wrong version or something)
> 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
> Attachments: HADOOP-11731-00.patch, HADOOP-11731-01.patch,
> HADOOP-11731-03.patch, HADOOP-11731-04.patch, HADOOP-11731-05.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)
