+1 (non-binding) Tested data source api , and jdbc data sources.
> On Jul 19, 2016, at 7:35 PM, Reynold Xin <r...@databricks.com> wrote: > > Please vote on releasing the following candidate as Apache Spark version > 2.0.0. The vote is open until Friday, July 22, 2016 at 20:00 PDT and passes > if a majority of at least 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Spark 2.0.0 > [ ] -1 Do not release this package because ... > > > The tag to be voted on is v2.0.0-rc5 > (13650fc58e1fcf2cf2a26ba11c819185ae1acc1f). > > This release candidate resolves ~2500 issues: > https://s.apache.org/spark-2.0.0-jira <https://s.apache.org/spark-2.0.0-jira> > > The release files, including signatures, digests, etc. can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-2.0.0-rc5-bin/ > <http://people.apache.org/~pwendell/spark-releases/spark-2.0.0-rc5-bin/> > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/pwendell.asc > <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-1195/ > <https://repository.apache.org/content/repositories/orgapachespark-1195/> > > The documentation corresponding to this release can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-2.0.0-rc5-docs/ > <http://people.apache.org/~pwendell/spark-releases/spark-2.0.0-rc5-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 from 1.x. > > ========================================== > What justifies a -1 vote for this release? > ========================================== > Critical bugs impacting major functionalities. > > Bugs already present in 1.x, missing features, or bugs related to new > features will not necessarily block this release. Note that historically > Spark documentation has been published on the website separately from the > main release so we do not need to block the release due to documentation > errors either. >
