4e7d8678a3
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. Author: Marcelo Vanzin <vanzin@cloudera.com> Closes #21515 from vanzin/SPARK-24372. |
||
---|---|---|
.. | ||
spark-rm | ||
do-release-docker.sh | ||
do-release.sh | ||
generate-contributors.py | ||
known_translations | ||
release-build.sh | ||
release-tag.sh | ||
release-util.sh | ||
releaseutils.py | ||
translate-contributors.py | ||
vote.tmpl |