hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14602) allow custom release notes/changelog during create-release
Date Wed, 28 Jun 2017 23:22:00 GMT

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

Chris Douglas commented on HADOOP-14602:
----------------------------------------

+1 to the patch. I didn't try running it, but it looks reasonable.
{noformat}
+    if [[ ! -d "${BASEDIR}/hadoop-common-project/hadoop-common/src/site/markdown/release/${HADOOP_VERSION}"
]]; then
+      hadoop_error "ERROR: ${BASEDIR}/hadoop-common-project/hadoop-common/src/site/markdown/release/${HADOOP_VERSION}
does not exist."
+      hadoop_error "ERROR: This directory and its contents are required to be manually created
for a security release."
+      exit 1
+    fi
{noformat}
We should probably add a section to the [wiki|https://wiki.apache.org/hadoop/HowToRelease]
on the expected contents, also so it can serve as a checklist for reviewers of the RC.

> 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, HADOOP-14602.01.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


Mime
View raw message