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, 03 Apr 2015 03:55:54 GMT

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

Allen Wittenauer commented on HADOOP-11731:
-------------------------------------------

bq. We won't update it since CHANGES.txt and jira summary are not supposed to be the same.

Wait, what?  The single line summary at the top of a JIRA isn't what you are putting in CHANGES.txt?
 I think you might be the *only* person who isn't using the summary line for the changes.txt
that who any sort of semi-regular commits.

bq. The entry in CHANGES.txt is a concise statement about the change committed.

In other words, exactly what the JIRA summary is supposed to be as well, but used prior to
commit.  





> 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
>             Fix For: 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)

Mime
View raw message