Hey Sean, This is being shipped now because there is a severe bug in 1.4.0 that can cause data corruption for Parquet users.
There are no blockers targeted for 1.4.1 - so I don't see that JIRA is inconsistent with shipping a release now. The goal of having every single targeted JIRA cleared by the time we start voting, I don't think there is broad consensus and cultural adoption of that principle yet. So I do not take it as a signal this release is premature (the story has been the same for every previous release we've ever done). The fact that we hit 90/124 of issues targeted at this release means we are targeting such that we get around 70% of issues merged. That actually doesn't seem so bad to me since there is some uncertainty in the process. B - Patrick On Wed, Jun 24, 2015 at 1:54 AM, Sean Owen <so...@cloudera.com> wrote: > There are 44 issues still targeted for 1.4.1. None are Blockers; 12 > are Critical. ~80% were opened and/or set by committers. Compare with > 90 issues resolved for 1.4.1. > > I'm concerned that committers are targeting lots more for a release > even in the short term than realistically can go in. On its face, it > suggests that an RC is premature. Why is 1.4.1 being put forth for > release now? It seems like people are saying they want a fair bit more > time to work on 1.4.1. > > I suspect that in fact people would rather untarget / slip (again) > these JIRAs, but it calls into question again how the targeting is > consistently off by this much. > > What unresolved JIRAs targeted for 1.4.1 are *really* still open for > 1.4.1? like, what would go badly if all 32 non-Critical JIRAs were > untargeted now? is the reality that there are a handful of items to > get in before the final release, and those are hopefully the ~12 > critical ones? How about some review of that before we ask people to > seriously test these bits? > > On Wed, Jun 24, 2015 at 8:37 AM, Patrick Wendell <pwend...@gmail.com> wrote: >> Please vote on releasing the following candidate as Apache Spark version >> 1.4.1! >> >> This release fixes a handful of known issues in Spark 1.4.0, listed here: >> http://s.apache.org/spark-1.4.1 >> >> The tag to be voted on is v1.4.1-rc1 (commit 60e08e5): >> https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h= >> 60e08e50751fe3929156de956d62faea79f5b801 >> >> The release files, including signatures, digests, etc. can be found at: >> http://people.apache.org/~pwendell/spark-releases/spark-1.4.1-rc1-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: >> [published as version: 1.4.1] >> https://repository.apache.org/content/repositories/orgapachespark-1118/ >> [published as version: 1.4.1-rc1] >> https://repository.apache.org/content/repositories/orgapachespark-1119/ >> >> The documentation corresponding to this release can be found at: >> http://people.apache.org/~pwendell/spark-releases/spark-1.4.1-rc1-docs/ >> >> Please vote on releasing this package as Apache Spark 1.4.1! >> >> The vote is open until Saturday, June 27, at 06:32 UTC and passes >> if a majority of at least 3 +1 PMC votes are cast. >> >> [ ] +1 Release this package as Apache Spark 1.4.1 >> [ ] -1 Do not release this package because ... >> >> To learn more about Apache Spark, please see >> http://spark.apache.org/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org >> For additional commands, e-mail: dev-h...@spark.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
