hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
Date Wed, 01 Apr 2015 23:37:55 GMT

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

Colin Patrick McCabe commented on HADOOP-11731:
-----------------------------------------------

I think we should support subtasks for now.  If we later decide they aren't important we can
make it optional in the script.

I actually am completely neutral on whether we should have release notes for multiple releases
in one file (or changes for CHANGES.txt).  I think if we want to change the format for upcoming
releases, we should discuss that on the mailing list first.  However, that issue shouldn't
hold up this patch.  It's easy enough to create a file with release notes for multiple releases
by cat'ing together files, or passing multiple revisions on the relnotes.py command line.

This is certainly a big improvement on what came before, so +1.

> 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, HADOOP-11731-06.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)

Mime
View raw message