I think the main point here is the testing of the release script, not the creation of the official release.
I think there should be an option to configure the release tool to use a forked github repo and/or a private playground nexus instead of official apache repos. In this case it would be easy to test regularly the tool, even by a non-committer (or even from Jenkins). But it would be just a smoketest of the release script... Marton ________________________________________ From: Allen Wittenauer <[email protected]> Sent: Wednesday, March 08, 2017 2:24 AM To: Andrew Wang Cc: Hadoop Common; [email protected]; Hdfs-dev; [email protected] Subject: Re: About 2.7.4 Release > On Mar 7, 2017, at 2:51 PM, Andrew Wang <[email protected]> wrote: > I think it'd be nice to > have a nightly Jenkins job that builds an RC, Just a reminder that any such build cannot be used for an actual release: http://www.apache.org/legal/release-policy.html#owned-controlled-hardware --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
