[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641320#comment-14641320
]
Andrew Wang commented on HADOOP-11731:
--------------------------------------
Cool. I'm going to start by pulling in the changes from the branch to
trunk/branch-2, and do whatever additional development is required there. Might
ping you for reviews.
bq. You only need it in common with the proper flags....
Hmm, so I work mostly on HDFS and Common, so would somewhat prefer not seeing
YARN and MR mixed in. If you feel very strongly I can do 4-in-1, but I'm also
willing to do the work to separate them out.
bq. It's not about backwards, it's about forwards....
We've kept the docs for branch-1 releases and I hope 2.7.x would have similar
legs, but fair enough. Do you have a sense for the state of JIRA fix versions?
If it's just a matter of running the script and fixing the dates, easy. If more
gardening is necessary, not so easy.
> 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: 2.7.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Fix For: 2.8.0, 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)
