GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/21515
[SPARK-24372][build] Add scripts to help with preparing releases.
The "do-release.sh" script asks questions about the RC being prepared,
trying to find out as much as possible automatically, and then executes
the existing scripts with proper arguments to prepare the release. This
script was used to prepare the 2.3.1 release candidates, so was tested
in that context.
The docker version runs that same script inside a docker image especially
crafted for building Spark releases. That image is based on the work
by Felix C. linked in the bug. At this point is has been only midly
tested.
I also added a template for the vote e-mail, with placeholders for
things that need to be replaced, although there is no automation around
that for the moment. It shouldn't be hard to hook up certain things like
version and tags to this, or to figure out certain things like the
repo URL from the output of the release scripts.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vanzin/spark SPARK-24372
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/21515.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #21515
----
commit 44454b69ff87a19dd6aa20e22e569e3d0811109b
Author: Marcelo Vanzin <vanzin@...>
Date: 2018-05-23T20:15:49Z
[SPARK-24372][build] Add scripts to help with preparing releases.
The "do-release.sh" script asks questions about the RC being prepared,
trying to find out as much as possible automatically, and then executes
the existing scripts with proper arguments to prepare the release. This
script was used to prepare the 2.3.1 release candidates, so was tested
in that context.
The docker version runs that same script inside a docker image especially
crafted for building Spark releases. That image is based on the work
by Felix C. linked in the bug. At this point is has been only midly
tested.
I also added a template for the vote e-mail, with placeholders for
things that need to be replaced, although there is no automation around
that for the moment. It shouldn't be hard to hook up certain things like
version and tags to this, or to figure out certain things like the
repo URL from the output of the release scripts.
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
