[
https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641369#comment-14641369
]
Allen Wittenauer commented on HADOOP-11731:
-------------------------------------------
bq. 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.
Yes, I feel *very* strongly about this one. Separating out the release notes
into subprojects may be one of the most end user unfriendly things we do (#1 is
the ridiculous number of incompatible changes). Again, as I pointed out above,
the *ONLY* people who truly, really care about these things being separated out
are the committers.... and, frankly, the reasoning there is void, given they
should know how to build their own set of notes if they really are too lazy to
grep them out.. Everyone else wants to see one file that has all the big
changes aka a single, consolidated release note file.
bq. 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.
I know that up to 2.6.0 is correct. But lint mode should tell you a lot about
people doing things like assigning multiple versions to a JIRA.
> 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)
