0001 Please vote on releasing the following candidate as Apache Spark version {version}.
0002
0003 The vote is open until {deadline} and passes if a majority +1 PMC votes are cast, with
0004 a minimum of 3 +1 votes.
0005
0006 [ ] +1 Release this package as Apache Spark {version}
0007 [ ] -1 Do not release this package because ...
0008
0009 To learn more about Apache Spark, please see https://spark.apache.org/
0010
0011 The tag to be voted on is {tag} (commit {tag_commit}):
0012 https://github.com/apache/spark/tree/{tag}
0013
0014 The release files, including signatures, digests, etc. can be found at:
0015 https://dist.apache.org/repos/dist/dev/spark/{tag}-bin/
0016
0017 Signatures used for Spark RCs can be found in this file:
0018 https://dist.apache.org/repos/dist/dev/spark/KEYS
0019
0020 The staging repository for this release can be found at:
0021 https://repository.apache.org/content/repositories/orgapachespark-{repo_id}/
0022
0023 The documentation corresponding to this release can be found at:
0024 https://dist.apache.org/repos/dist/dev/spark/{tag}-docs/
0025
0026 The list of bug fixes going into {version} can be found at the following URL:
0027 https://issues.apache.org/jira/projects/SPARK/versions/{jira_version_id}
0028
0029 FAQ
0030
0031 =========================
0032 How can I help test this release?
0033 =========================
0034
0035 If you are a Spark user, you can help us test this release by taking
0036 an existing Spark workload and running on this release candidate, then
0037 reporting any regressions.
0038
0039 If you're working in PySpark you can set up a virtual env and install
0040 the current RC and see if anything important breaks, in the Java/Scala
0041 you can add the staging repository to your projects resolvers and test
0042 with the RC (make sure to clean up the artifact cache before/after so
0043 you don't end up building with a out of date RC going forward).
0044
0045 ===========================================
0046 What should happen to JIRA tickets still targeting {version}?
0047 ===========================================
0048
0049 The current list of open tickets targeted at {version} can be found at:
0050 {open_issues_link}
0051
0052 Committers should look at those and triage. Extremely important bug
0053 fixes, documentation, and API tweaks that impact compatibility should
0054 be worked on immediately. Everything else please retarget to an
0055 appropriate release.
0056
0057 ==================
0058 But my bug isn't fixed?
0059 ==================
0060
0061 In order to make timely releases, we will typically not hold the
0062 release unless the bug in question is a regression from the previous
0063 release. That being said, if there is something which is a regression
0064 that has not been correctly targeted please ping me or a committer to
0065 help target the issue.
