No 1.4.0 Blockers at this point, which is great. Forking this thread to discuss something else.
There are 92 issues targeted for 1.4.0, 28 of which are marked Critical. Many are procedural issues like "update docs for 1.4" or "check X for 1.4". Are these resolved? They sound like things that are definitely supposed to have finished by now. Certainly, almost all of these are not going to be resolved for 1.4.0. Is this something we should be concerned about? because they are predominantly filed by or assigned to committers, not inexperienced contributors. I'm concerned that Target Version loses meaning if this happens frequently, and this number is ~10% of all JIRAs for 1.4. It's tempting to say X is important and someone will do X before 1.4, and then forget about it since it has been safely noted for later. Meanwhile other issues that grab more immediate attention and get worked on. This constitutes a form of project management, but de facto it's ad-hoc and reactive. Look at how many new issues and changes have still been coming in since the first release candidate of 1.4.0, compared to those "targeted" for the release. In an ideal world, Target Version really is what's going to go in as far as anyone knows and when new stuff comes up, we all have to figure out what gets dropped to fit by the release date. Boring, standard software project management practice. I don't know how realistic that is, but, I'm wondering how people feel about this, who have filed these JIRAs? Concretely, should non-Critical issues for 1.4.0 be un-Targeted? should they all be un-Targeted after the release? On Fri, May 29, 2015 at 7:40 PM, Patrick Wendell <pwend...@gmail.com> wrote: > Please vote on releasing the following candidate as Apache Spark version > 1.4.0! > > The tag to be voted on is v1.4.0-rc3 (commit dd109a8): > https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h=dd109a8746ec07c7c83995890fc2c0cd7a693730 > > The release files, including signatures, digests, etc. can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.4.0-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: > [published as version: 1.4.0] > https://repository.apache.org/content/repositories/orgapachespark-1109/ > [published as version: 1.4.0-rc3] > https://repository.apache.org/content/repositories/orgapachespark-1110/ > > The documentation corresponding to this release can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.4.0-rc3-docs/ > > Please vote on releasing this package as Apache Spark 1.4.0! > > The vote is open until Tuesday, June 02, at 00: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.0 > [ ] -1 Do not release this package because ... > > To learn more about Apache Spark, please see > http://spark.apache.org/ > > == What has changed since RC1 == > Below is a list of bug fixes that went into this RC: > http://s.apache.org/vN > > == How can I help test this release? == > If you are a Spark user, you can help us test this release by > taking a Spark 1.3 workload and running on this release candidate, > then reporting any regressions. > > == What justifies a -1 vote for this release? == > This vote is happening towards the end of the 1.4 QA period, > so -1 votes should only occur for significant regressions from 1.3.1. > Bugs already present in 1.3.X, minor regressions, or bugs related > to new features will not block this release. > > --------------------------------------------------------------------- > 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
