hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
Date Fri, 24 Jul 2015 23:58:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641267#comment-14641267

Allen Wittenauer commented on HADOOP-11731:

bq. Fix the -Preleasedocs profile (looks like we need the per-project logic? I only see it
in common's pom right now)

You only need it in common with the proper flags.  The generated website points to the index
which contains all of them. Separating them out is only useful to maybe some of the PMC and
committers.  Everyone else treats Hadoop as one package.  Pretending otherwise is dumb.

bq. You mentioned the HowToRelease wiki instructions being incorrect, but I didn't catch what
exactly was off. It says to close the JIRAs as the last step, which still seems okay.

There's some other stuff, but I don't remember off the top of my head.  It mainly had to do
with the date reported in the generated notes vs. the tar ball and keeping them in sync.

bq. Regarding the index, are you recommending we run the script for historical releases? 


bq. Since we still host the docs for prior releases, seems like people could just look at
the old CHANGES.txt there.

It's not about backwards, it's about forwards.  At some point, (probably Hadoop 2.12 or Hadoop
2.13, say autumn 2017 given current pace), there will be no more releases on the website that
still have a CHANGES.txt file.   Then what?  If we generate the historical data, the answer
is obvious.

> 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

View raw message