This vote is cancelled in favor of RC2.
On Tue, Jan 27, 2015 at 4:20 PM, Reynold Xin wrote:
> +1
>
> Tested on Mac OS X
>
> On Tue, Jan 27, 2015 at 12:35 PM, Krishna Sankar
> wrote:
>>
>> +1
>> 1. Compiled OSX 10.10 (Yosemite) OK Total time: 12:55 min
>> mvn clean package -Pyarn -Dyarn.vers
+1
Tested on Mac OS X
On Tue, Jan 27, 2015 at 12:35 PM, Krishna Sankar
wrote:
> +1
> 1. Compiled OSX 10.10 (Yosemite) OK Total time: 12:55 min
> mvn clean package -Pyarn -Dyarn.version=2.6.0 -Phadoop-2.4
> -Dhadoop.version=2.6.0 -Phive -DskipTests
> 2. Tested pyspark, mlib - running as wel
+1
1. Compiled OSX 10.10 (Yosemite) OK Total time: 12:55 min
mvn clean package -Pyarn -Dyarn.version=2.6.0 -Phadoop-2.4
-Dhadoop.version=2.6.0 -Phive -DskipTests
2. Tested pyspark, mlib - running as well as compare results with 1.1.x &
1.2.0
2.1. statistics OK
2.2. Linear/Ridge/Laso Regression
Okay - we've resolved all issues with the signatures and keys.
However, I'll leave the current vote open for a bit to solicit
additional feedback.
On Tue, Jan 27, 2015 at 10:43 AM, Sean McNamara
wrote:
> Sounds good, that makes sense.
>
> Cheers,
>
> Sean
>
>> On Jan 27, 2015, at 11:35 AM, Patric
Sounds good, that makes sense.
Cheers,
Sean
> On Jan 27, 2015, at 11:35 AM, Patrick Wendell wrote:
>
> Hey Sean,
>
> Right now we don't publish every 2.11 binary to avoid combinatorial
> explosion of the number of build artifacts we publish (there are other
> parameters such as whether hive i
Hey Sean,
Right now we don't publish every 2.11 binary to avoid combinatorial
explosion of the number of build artifacts we publish (there are other
parameters such as whether hive is included, etc). We can revisit this
in future feature releases, but .1 releases like this are reserved for
bug fix
We’re using spark on scala 2.11 /w hadoop2.4. Would it be practical / make
sense to build a bin version of spark against scala 2.11 for versions other
than just hadoop1 at this time?
Cheers,
Sean
> On Jan 27, 2015, at 12:04 AM, Patrick Wendell wrote:
>
> Please vote on releasing the follow
Yes - the key issue is just due to me creating new keys this time
around. Anyways let's take another stab at this. In the mean time,
please don't hesitate to test the release itself.
- Patrick
On Tue, Jan 27, 2015 at 10:00 AM, Sean Owen wrote:
> Got it. Ignore the SHA512 issue since these aren't
Got it. Ignore the SHA512 issue since these aren't somehow expected by
a policy or Maven to be in a certain format. Just wondered if the
difference was intended.
The Maven way of generated the SHA1 hashes is to set this on the
install plugin, AFAIK, although I'm not sure if the intent was to hash
Hey Sean,
The release script generates hashes in two places (take a look a bit
further down in the script), one for the published artifacts and the
other for the binaries. In the case of the binaries we use SHA512
because, AFAIK, the ASF does not require you to use SHA1 and SHA512 is
better. In th
I think there are several signing / hash issues that should be fixed
before this release.
Hashes:
http://issues.apache.org/jira/browse/SPARK-5308
https://github.com/apache/spark/pull/4161
The hashes here are correct, but have two issues:
As noted in the JIRA, the format of the hash file is "non
Please vote on releasing the following candidate as Apache Spark version 1.2.1!
The tag to be voted on is v1.2.1-rc1 (commit 3e2d7d3):
https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h=3e2d7d310b76c293b9ac787f204e6880f508f6ec
The release files, including signatures, digests, etc. can
12 matches
Mail list logo
