I tested RC3 on CentOS 7.3.1611/OpenJDK 1.8.0_121/R 3.3.3
with `-Pyarn -Phadoop-2.7 -Pkinesis-asl -Phive -Phive-thriftserver –Psparkr`

At the end of R test, I saw `Had CRAN check errors; see logs.`,
but tests passed and log file looks good.


From: Reynold Xin <rxin@databricks.com>
Date: Wednesday, April 19, 2017 at 3:41 PM
To: Marcelo Vanzin <vanzin@cloudera.com>
Cc: Michael Armbrust <michael@databricks.com>, "dev@spark.apache.org" <dev@spark.apache.org>
Subject: Re: [VOTE] Apache Spark 2.1.1 (RC3)


On Wed, Apr 19, 2017 at 3:31 PM, Marcelo Vanzin <vanzin@cloudera.com> wrote:
+1 (non-binding).

Ran the hadoop-2.6 binary against our internal tests and things look good.

On Tue, Apr 18, 2017 at 11:59 AM, Michael Armbrust
<michael@databricks.com> wrote:
> Please vote on releasing the following candidate as Apache Spark version
> 2.1.1. The vote is open until Fri, April 21st, 2018 at 13:00 PST and passes
> if a majority of at least 3 +1 PMC votes are cast.
> [ ] +1 Release this package as Apache Spark 2.1.1
> [ ] -1 Do not release this package because ...
> To learn more about Apache Spark, please see http://spark.apache.org/
> The tag to be voted on is v2.1.1-rc3
> (2ed19cff2f6ab79a718526e5d16633412d8c4dd4)
> List of JIRA tickets resolved can be found with this filter.
> The release files, including signatures, digests, etc. can be found at:
> http://home.apache.org/~pwendell/spark-releases/spark-2.1.1-rc3-bin/
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/pwendell.asc
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1230/
> The documentation corresponding to this release can be found at:
> http://people.apache.org/~pwendell/spark-releases/spark-2.1.1-rc3-docs/
> How can I help test this release?
> If you are a Spark user, you can help us test this release by taking an
> existing Spark workload and running on this release candidate, then
> reporting any regressions.
> What should happen to JIRA tickets still targeting 2.1.1?
> Committers should look at those and triage. Extremely important bug fixes,
> documentation, and API tweaks that impact compatibility should be worked on
> immediately. Everything else please retarget to 2.1.2 or 2.2.0.
> But my bug isn't fixed!??!
> In order to make timely releases, we will typically not hold the release
> unless the bug in question is a regression from 2.1.0.
> What happened to RC1?
> There were issues with the release packaging and as a result was skipped.


To unsubscribe e-mail: dev-unsubscribe@spark.apache.org