Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <CAAswR-5WsaWHzp1S=SP3BUpbyxfL9F9Wk8xkBqqr4_94T6of6Q@mail.gmail.com>
References: <CAAswR-756cSsvZGRq6s2_v23gNTRft2rTb5p+i0F5Vgoc7WTgg@mail.gmail.com>
 <OF4FB37E39.F9099B76-ON4925811B.00314EAA-4925811B.00317494@notes.na.collabserv.com>
 <CAAswR-5WsaWHzp1S=SP3BUpbyxfL9F9Wk8xkBqqr4_94T6of6Q@mail.gmail.com>
From: Marcelo Vanzin <vanzin@cloudera.com>
Date: Thu, 11 May 2017 15:08:15 -0700
Message-ID: <CAAOnQ7uRcbu7OEO4D04aDE3HMABN190i+KR9DOZSe7cR2dS=8g@mail.gmail.com>
Subject: Re: [VOTE] Apache Spark 2.2.0 (RC2)
To: Michael Armbrust <michael@databricks.com>
Cc: "dev@spark.apache.org" <dev@spark.apache.org>
Content-Type: text/plain; charset="UTF-8"
archived-at: Thu, 11 May 2017 22:08:22 -0000

Since you'll be creating a new RC, I'd wait until SPARK-20666 is
fixed, since the change that caused it is in branch-2.2. Probably a
good idea to raise it to blocker at this point.

On Thu, May 11, 2017 at 2:59 PM, Michael Armbrust
<michael@databricks.com> wrote:
> I'm going to -1 given the outstanding issues and lack of +1s.  I'll create
> another RC once ML has had time to take care of the more critical problems.
> In the meantime please keep testing this release!
>
> On Tue, May 9, 2017 at 2:00 AM, Kazuaki Ishizaki <ISHIZAKI@jp.ibm.com>
> wrote:
>>
>> +1 (non-binding)
>>
>> I tested it on Ubuntu 16.04 and OpenJDK8 on ppc64le. All of the tests for
>> core have passed.
>>
>> $ java -version
>> openjdk version "1.8.0_111"
>> OpenJDK Runtime Environment (build
>> 1.8.0_111-8u111-b14-2ubuntu0.16.04.2-b14)
>> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>> $ build/mvn -DskipTests -Phive -Phive-thriftserver -Pyarn -Phadoop-2.7
>> package install
>> $ build/mvn -Phive -Phive-thriftserver -Pyarn -Phadoop-2.7 test -pl core
>> ...
>> Run completed in 15 minutes, 12 seconds.
>> Total number of tests run: 1940
>> Suites: completed 206, aborted 0
>> Tests: succeeded 1940, failed 0, canceled 4, ignored 8, pending 0
>> All tests passed.
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 16:51 min
>> [INFO] Finished at: 2017-05-09T17:51:04+09:00
>> [INFO] Final Memory: 53M/514M
>> [INFO]
>> ------------------------------------------------------------------------
>> [WARNING] The requested profile "hive" could not be activated because it
>> does not exist.
>>
>>
>> Kazuaki Ishizaki,
>>
>>
>>
>> From:        Michael Armbrust <michael@databricks.com>
>> To:        "dev@spark.apache.org" <dev@spark.apache.org>
>> Date:        2017/05/05 02:08
>> Subject:        [VOTE] Apache Spark 2.2.0 (RC2)
>> ________________________________
>>
>>
>>
>> Please vote on releasing the following candidate as Apache Spark version
>> 2.2.0. The vote is open until Tues, May 9th, 2017 at 12:00 PST and passes if
>> a majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Spark 2.2.0
>> [ ] -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 v2.2.0-rc2
>> (1d4017b44d5e6ad156abeaae6371747f111dd1f9)
>>
>> List of JIRA tickets resolved can be found with this filter.
>>
>> The release files, including signatures, digests, etc. can be found at:
>> http://home.apache.org/~pwendell/spark-releases/spark-2.2.0-rc2-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-1236/
>>
>> The documentation corresponding to this release can be found at:
>> http://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc2-docs/
>>
>>
>> FAQ
>>
>> 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.
>>
>> What should happen to JIRA tickets still targeting 2.2.0?
>>
>> Committers should look at those and triage. Extremely important bug fixes,
>> documentation, and API tweaks that impact compatibility should be worked on
>> immediately. Everything else please retarget to 2.3.0 or 2.2.1.
>>
>> But my bug isn't fixed!??!
>>
>> In order to make timely releases, we will typically not hold the release
>> unless the bug in question is a regression from 2.1.1.
>>
>


-- 
Marcelo

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