Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <CAPh_B=Z7D9RPkPcwhbjrh7nRjAA+m2QXXKKzzj6LAbwgbezY3w@mail.gmail.com>
References: <CAPh_B=Z7D9RPkPcwhbjrh7nRjAA+m2QXXKKzzj6LAbwgbezY3w@mail.gmail.com>
From: Marcelo Vanzin <vanzin@cloudera.com>
Date: Thu, 29 Sep 2016 15:17:04 -0700
Message-ID: <CAAOnQ7v+4QQxnbax1ycBesPCU7HVRT7fyFxanUJNHe43xUF-6g@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Spark 2.0.1 (RC4)
To: Reynold Xin <rxin@databricks.com>
Cc: "dev@spark.apache.org" <dev@spark.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Thu, 29 Sep 2016 22:17:14 -0000

+1

On Wed, Sep 28, 2016 at 7:14 PM, Reynold Xin <rxin@databricks.com> wrote:
> Please vote on releasing the following candidate as Apache Spark version
> 2.0.1. The vote is open until Sat, Oct 1, 2016 at 20: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.1
> [ ] -1 Do not release this package because ...
>
>
> The tag to be voted on is v2.0.1-rc4
> (933d2c1ea4e5f5c4ec8d375b5ccaa4577ba4be38)
>
> This release candidate resolves 301 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-rc4-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-1203/
>
> The documentation corresponding to this release can be found at:
> http://people.apache.org/~pwendell/spark-releases/spark-2.0.1-rc4-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. RC5) is cut, I will change the fix version of those patches to 2.0.1.
>
>


-- 
Marcelo

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscribe@spark.apache.org