So technically the vote has passed, but IMHO it does not make sense to release this and then immediately release 2.0.2. I will work on a new RC once SPARK-17666 and SPARK-17673 are fixed.
Please shout if you disagree. On Tue, Sep 27, 2016 at 2:05 PM, Mark Hamstra <m...@clearstorydata.com> wrote: > If we're going to cut another RC, then it would be good to get this in as > well (assuming that it is merged shortly): https://github.com/ > apache/spark/pull/15213 > > It's not a regression, and it shouldn't happen too often, but when failed > stages don't get resubmitted it is a fairly significant issue. > > On Tue, Sep 27, 2016 at 1:31 PM, Reynold Xin <r...@databricks.com> wrote: > >> Actually I'm going to have to -1 the release myself. Sorry for crashing >> the party, but I saw two super critical issues discovered in the last 2 >> days: >> >> https://issues.apache.org/jira/browse/SPARK-17666 -- this would >> eventually hang Spark when running against S3 (and many other storage >> systems) >> >> https://issues.apache.org/jira/browse/SPARK-17673 -- this is a >> correctness issue across all non-file data sources. >> >> If we go ahead and release 2.0.1 based on this RC, we would need to cut >> 2.0.2 immediately. >> >> >> >> >> >> On Tue, Sep 27, 2016 at 10:18 AM, Mark Hamstra <m...@clearstorydata.com> >> wrote: >> >>> I've got a couple of build niggles that should really be investigated at >>> some point (what look to be OOM issues in spark-repl when building and >>> testing with mvn in a single pass instead of in two passes with -DskipTests >>> first; the killing of ssh sessions by YarnClusterSuite), but these >>> aren't anything that should hold up the release. >>> >>> +1 >>> >>> On Sat, Sep 24, 2016 at 3:08 PM, Reynold Xin <r...@databricks.com> >>> wrote: >>> >>>> Please vote on releasing the following candidate as Apache Spark >>>> version 2.0.1. The vote is open until Tue, Sep 27, 2016 at 15:30 PDT and >>>> passes if a majority of at least 3+1 PMC votes are cast. >>>> >>>> [ ] +1 Release this package as Apache Spark 2.0.1 >>>> [ ] -1 Do not release this package because ... >>>> >>>> >>>> The tag to be voted on is v2.0.1-rc3 (9d28cc10357a8afcfb2fa2e6eecb5 >>>> c2cc2730d17) >>>> >>>> This release candidate resolves 290 issues: >>>> https://s.apache.org/spark-2.0.1-jira >>>> >>>> The release files, including signatures, digests, etc. can be found at: >>>> http://people.apache.org/~pwendell/spark-releases/spark-2.0.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-1201/ >>>> >>>> The documentation corresponding to this release can be found at: >>>> http://people.apache.org/~pwendell/spark-releases/spark-2.0.1-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.0. >>>> >>>> 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.0, 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.2, rather than 2.0.1. If a new RC >>>> (i.e. RC4) is cut, I will change the fix version of those patches to 2.0.1. >>>> >>>> >>>> >>> >> >
