My bad, RC7 out now!

Binaries:
https://repository.apache.org/content/repositories/orgapachemahout-1066/org/apache/mahout/apache-mahout-distribution/14.1/

Source:
https://repository.apache.org/content/repositories/orgapachemahout-1066/org/apache/mahout/mahout/14.1/

On Fri, Sep 11, 2020 at 1:04 AM Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> Hi,
>
> Sad to see you didn't merge my changes in "issue/MAHOUT-2117" back to
> master before cutting the next RC :-(
>
> So I'm not going to vote this time as the result would be the same as last
> time ...
>
> Chris
>
>
> Am 11.09.20, 03:17 schrieb "Trevor Grant" <trevor.d.gr...@gmail.com>:
>
>     Thank you so much for getting this out Andrew.
>
>     I verified all checksums/sigs.
>
>     I successfully built the source including all tests. (I did this in the
>     public docker container rawkintrevo/mahout-builder-base)
>
>     I also tested the binaries in the public docker container
>     rawkintrevo/mahoutgui , but bashing into the running container,
> unpacking
>     both the binary archives, and then aiming and running the mahout
> example
>     notebook in turn against each of the unpacked binaries from each of the
>     archives.  I did this in place of spark-shell, as I think it's a more
>     elegant solution going forward, but would encourage others to test
> against
>     mahout spark-shell.
>
>     So given all of that, I give an enthusiastic +1
>
>     On Thu, Sep 10, 2020 at 3:37 PM Andrew Musselman <a...@apache.org>
> wrote:
>
>     > Binaries:
>     >
>     >
> https://repository.apache.org/content/repositories/orgapachemahout-1065/org/apache/mahout/apache-mahout-distribution/14.1/
>     >
>     > Source:
>     >
>     >
> https://repository.apache.org/content/repositories/orgapachemahout-1065/org/apache/mahout/mahout/14.1/
>     >
>     > Please check checksums and signatures, run the shell, do some
> computation,
>     > run your favorite jobs, and let us know how it looks.
>     >
>     > Thanks!
>     >
>     > Best
>     > Andrew
>     >
>
>

Reply via email to