[
https://issues.apache.org/jira/browse/HADOOP-11793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639701#comment-14639701
]
Allen Wittenauer commented on HADOOP-11793:
-------------------------------------------
The reason why the lint mode was added so that create-release would
purposefully stop the build so that the RM could fix issues in JIRA prior to
cutting the release. So create-release ideally would have this change *and*
another one to independently call releasedocmaker in lint mode very early on.
Additionally, the wiki page on how to actually use create release needs to be
majorly updated with steps re-arranged, otherwise Bad Things(tm) will happen.
In particular, closing the release out in jira means those issues cannot be
updated. (e.g., YARN-3614 will probably never show up in releasedocmaker output
because it was Fixed incorrectly and then subsequently closed by the RM.)
> Update create-release for releasedocmaker.py
> --------------------------------------------
>
> Key: HADOOP-11793
> URL: https://issues.apache.org/jira/browse/HADOOP-11793
> Project: Hadoop Common
> Issue Type: Task
> Components: build
> Affects Versions: 2.8.0
> Reporter: Allen Wittenauer
> Assignee: ramtin
> Attachments: HADOOP-11793.001.patch
>
>
> With the commit of HADOOP-11731, the changelog and release note data is now
> automated with the build. The create-release script needs to do the correct
> thing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
