+1 On Tue, Nov 8, 2016 at 1:17 PM, Sean Owen <so...@cloudera.com> wrote:
> +1 binding > > (See comments on last vote; same results, except, the regression we > identified is fixed now.) > > > On Tue, Nov 8, 2016 at 6:10 AM Reynold Xin <r...@databricks.com> wrote: > >> Please vote on releasing the following candidate as Apache Spark version >> 2.0.2. The vote is open until Thu, Nov 10, 2016 at 22: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.2 >> [ ] -1 Do not release this package because ... >> >> >> The tag to be voted on is v2.0.2-rc3 (584354eaac02531c9584188b143367 >> ba694b0c34) >> >> This release candidate resolves 84 issues: https://s.apache.org/spark-2. >> 0.2-jira >> >> The release files, including signatures, digests, etc. can be found at: >> http://people.apache.org/~pwendell/spark-releases/spark-2.0.2-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-1214/ >> >> The documentation corresponding to this release can be found at: >> http://people.apache.org/~pwendell/spark-releases/spark-2.0.2-rc3-docs/ >> >> >> Q: How can I help test this release? >> A: 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 2.0.1. >> >> Q: What justifies a -1 vote for this release? >> A: This is a maintenance release in the 2.0.x series. Bugs already >> present in 2.0.1, missing features, or bugs related to new features will >> not necessarily block this release. >> >> Q: What fix version should I use for patches merging into branch-2.0 from >> now on? >> A: Please mark the fix version as 2.0.3, rather than 2.0.2. If a new RC >> (i.e. RC4) is cut, I will change the fix version of those patches to 2.0.2. >> >
