You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2017/06/28 00:39:00 UTC
[jira] [Commented] (HADOOP-14602) allow custom release
notes/changelog during create-release
[ https://issues.apache.org/jira/browse/HADOOP-14602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065734#comment-16065734 ]
Chris Douglas commented on HADOOP-14602:
----------------------------------------
Only skimmed the patch so this may be obvious in context, but --security sets SECURITYRELEASE while {{makearelease}} checks "$\{SECURITY\}" == true ?
> allow custom release notes/changelog during create-release
> ----------------------------------------------------------
>
> Key: HADOOP-14602
> URL: https://issues.apache.org/jira/browse/HADOOP-14602
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, scripts
> Affects Versions: 3.0.0-alpha3
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Minor
> Attachments: HADOOP-14602.00.patch
>
>
> When doing a security release, we may not want to change JIRA to reflect that such a release is coming. Therefore, it would be nice to provide custom-made versions instead of allowing releasedocs to run. Since other features may require tweaking during a security release, let's create a --security flag which disables this behavior and potentially future behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org