spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hamstra <m...@clearstorydata.com>
Subject Re: [VOTE] Release Apache Spark 1.6.1 (RC1)
Date Thu, 03 Mar 2016 05:39:42 GMT
+1

On Wed, Mar 2, 2016 at 2:45 PM, Michael Armbrust <michael@databricks.com>
wrote:

> Please vote on releasing the following candidate as Apache Spark version
> 1.6.1!
>
> The vote is open until Saturday, March 5, 2016 at 20:00 UTC and passes if
> a majority of at least 3+1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Spark 1.6.1
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see http://spark.apache.org/
>
> The tag to be voted on is *v1.6.1-rc1
> (15de51c238a7340fa81cb0b80d029a05d97bfc5c)
> <https://github.com/apache/spark/tree/v1.6.1-rc1>*
>
> The release files, including signatures, digests, etc. can be found at:
> https://home.apache.org/~pwendell/spark-releases/spark-1.6.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:
> https://repository.apache.org/content/repositories/orgapachespark-1180/
>
> The test repository (versioned as v1.6.1-rc1) for this release can be
> found at:
> https://repository.apache.org/content/repositories/orgapachespark-1179/
>
> The documentation corresponding to this release can be found at:
> https://home.apache.org/~pwendell/spark-releases/spark-1.6.1-rc1-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.6.0.
>
> ================================================
> == What justifies a -1 vote for this release? ==
> ================================================
> This is a maintenance release in the 1.6.x series.  Bugs already present
> in 1.6.0, missing features, or bugs related to new features will not
> necessarily block this release.
>
> ===============================================================
> == What should happen to JIRA tickets still targeting 1.6.0? ==
> ===============================================================
> 1. It is OK for documentation patches to target 1.6.1 and still go into
> branch-1.6, since documentations will be published separately from the
> release.
> 2. New features for non-alpha-modules should target 1.7+.
> 3. Non-blocker bug fixes should target 1.6.2 or 2.0.0, or drop the target
> version.
>

Mime
View raw message