hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11731) Rework the changelog and releasenotes
Date Thu, 02 Apr 2015 21:16:36 GMT

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

Tsz Wo Nicholas Sze commented on HADOOP-11731:
----------------------------------------------

Generating change log from JIRA is a good idea.  It bases on an assumption that each JIRA
has an accurate summary (a.k.a. JIRA title) to reflect the committed change. Unfortunately,
the assumption is invalid for many cases since we never enforce that the JIRA summary must
be the same as the change log.  Have you compared the current CHANGES.txt with the generated
change log?  I beg the diff is long.

Besides, after a release R1 is out, someone may (accidentally or intentionally) modify the
JIRA summary.  Then, the entry for the same item in a later release R2 could be different
from the one in R1.

Yet another concern is that non-committers can add/edit JIRA summary but only committers could
modify CHANGES.txt.

I agree that manually editing CHANGES.txt is not a perfect solution.  However, it worked well
in the past for many releases.  I suggest we keep the current dev workflow.  Try using the
new script provided here to generate the next release.  If everything works well, we shell
remove CHANGES.txt and revise the dev workflow.  What do you think?

> 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