Tommy Naugle created MAHOUT-2195:
Summary: Broken Link - Documentation/Developers Guide/How to
Release 2
Key: MAHOUT-2195
URL: https://issues.apache.org/jira/browse/MAHOUT-2195
Project: Mahout
Tommy Naugle created MAHOUT-2194:
Summary: Broken Link - Documentation/Developers Guide/How to
Release
Key: MAHOUT-2194
URL: https://issues.apache.org/jira/browse/MAHOUT-2194
Project: Mahout
Tommy Naugle created MAHOUT-2182:
Summary: Broken Link - Download/Latest Release
Key: MAHOUT-2182
URL: https://issues.apache.org/jira/browse/MAHOUT-2182
Project: Mahout
Issue Type
gt; Looking through our log I see some small improvements along with a new
> > version of ridge regression that haven't made it into a release.
> >
> > Along with that there are several tickets that would be good to get done
> > and into a release, including:
&g
On 2 (log4j) iirc, we didn't since the vulnerability only affects log4j 2.x
and we're on 1.x
tg
On Thu, Feb 16, 2023 at 1:42 PM Andrew Musselman wrote:
> Looking through our log I see some small improvements along with a new
> version of ridge regression that haven't made it into a r
Looking through our log I see some small improvements along with a new
version of ridge regression that haven't made it into a release.
Along with that there are several tickets that would be good to get done
and into a release, including:
Build failed on AArch64, Fedora 33:
https
> wrote:
> > >
> > > > YAYYY!!! :-)
> > > >
> > > > Congrats to us all :-)
> > > >
> > > > Chris
> > > >
> > > > Am 08.1
; > wrote:
> > >
> > > > YAYYY!!! :-)
> > > >
> > > > Congrats to us all :-)
> > > >
> > > > Chris
> > > >
> > > > Am 08.10.20, 16:13 schrieb "
is
> > >
> > > Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
> > >
> > > The Apache Mahout PMC is pleased to announce the release of
> Mahout
> > > 14.1.
> > > Mahout's goal
> > Congrats to us all :-)
> > >
> > > Chris
> > >
> > > Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
> > >
> > > The Apache Mahout PMC is pleased to announce the release of
> Mahout
> > > 14
t; Happy days!
>
> On Thu, Oct 8, 2020 at 7:26 AM Christofer Dutz
> wrote:
>
> > YAYYY!!! :-)
> >
> > Congrats to us all :-)
> >
> > Chris
> >
> > Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
>
;
> > Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
> >
> > The Apache Mahout PMC is pleased to announce the release of Mahout
> > 14.1.
> > Mahout's goal is to create an environment for quickly creating
> > machine-learning applications that scale and ru
Happy days!
On Thu, Oct 8, 2020 at 7:26 AM Christofer Dutz
wrote:
> YAYYY!!! :-)
>
> Congrats to us all :-)
>
> Chris
>
> Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
>
> The Apache Mahout PMC is pleased to announce the release of Mahout
>
YAYYY!!! :-)
Congrats to us all :-)
Chris
Am 08.10.20, 16:13 schrieb "Andrew Musselman" :
The Apache Mahout PMC is pleased to announce the release of Mahout 14.1.
Mahout's goal is to create an environment for quickly creating
machine-learning applications that sca
The Apache Mahout PMC is pleased to announce the release of Mahout 14.1.
Mahout's goal is to create an environment for quickly creating
machine-learning applications that scale and run on the highest-performance
parallel computation engines available. Mahout comprises an interactive
environment
YAY!!!
Am 30.09.20, 20:23 schrieb "Andrew Musselman" :
Thanks Pat! That makes four binding +1s, two non-binding +1s (thanks Joe
and Chris), and no -1s.
Vote passes and we will go ahead and release this build.
Appreciate everyone's time to get this one out; m
Thanks Pat! That makes four binding +1s, two non-binding +1s (thanks Joe
and Chris), and no -1s.
Vote passes and we will go ahead and release this build.
Appreciate everyone's time to get this one out; many thanks to Chris Dutz
for his major contribution with this build refactor, which made my
Still haven’t had a chance to test since it will take some experimentation
to figure out jars needed etc. My test is to replace 0.13 with 0.14.1
Still I see no reason to delay the release for my slow testing
+1
From: Andrew Musselman
Reply: dev@mahout.apache.org
Date: September 28, 2020
e focus on documentation in the
> next release, we can get things clear.
>
>
>
>
>
>
>
>
>
>
>
> From: Andrew Palumbo
>
> Sent: Wednesday, September 23, 2020 9:29 PM
>
> To: priv...@mahout.apache.org
>
> Subject: Re:
steps to verify
things are working; for now could you try the spark-shell commands I posted
yesterday?
On Fri, Sep 25, 2020 at 11:19 PM Jake Mannix wrote:
> Howdy all. Andrew asked me to take a little time and verify the release so
>
> we could get another PMC +1, so I tried to dust off
Howdy all. Andrew asked me to take a little time and verify the release so
we could get another PMC +1, so I tried to dust off my Mahout skills and
help out... but frankly, the "getting started" from a binary distribution
docs are pretty hard for _me_ to follow.
I start on the
I am +1 (binding) on this release; I have:
(1) Downloaded both binary and source releases
(2) Verified checksums and signatures
(3) Built from source
(4) Run the spark-shell, and loaded and run the sparse DRM multiplier
function for both distros:
Note that in the source build the shell script
Thanks Joe
On Fri, Sep 25, 2020 at 1:32 PM Joe Olson wrote:
> +1 non binding, checked the sigs. Built, all tests passed, Java 8 Docker
>
>
+1 non binding, checked the sigs. Built, all tests passed, Java 8 Docker
t's still up next week I can vote.
>
> On Wed, Sep 16, 2020, 11:27 AM Christofer Dutz
> wrote:
>
>> +1 (non-binding)
>>
>> Chris
>>
>> [OK] Download all staged artifacts under the url specified in the release
>> vote email into a directory we’ll now
ght I hope.
>>
>> Pat can give a binding, and knows the most about the SBT- so I'd like to
>> see a +1 from him (or -1 if it doesn't work).
>>
>> I have a binding.
>>
>> Implicitly, AKM would have a binding +1, but the release master normally
>> doesn'
; I have a binding.
>
> Implicitly, AKM would have a binding +1, but the release master normally
> doesn't vote until the end.
>
> So that would be 3, but it would be worth exploring a new PMC addition.
>
> On Tue, Sep 22, 2020 at 2:25 AM Christofer Dutz >
> wrote:
>
> &
I'm back- will test tonight I hope.
Pat can give a binding, and knows the most about the SBT- so I'd like to
see a +1 from him (or -1 if it doesn't work).
I have a binding.
Implicitly, AKM would have a binding +1, but the release master normally
doesn't vote until the end.
So that would be 3
as we have the
release out the door.
Chris
Away from my computer on vacation- if it's still up next week I can vote.
On Wed, Sep 16, 2020, 11:27 AM Christofer Dutz
wrote:
> +1 (non-binding)
>
> Chris
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email into a directory we’ll now
Chris, Pat was asking about the new module structure so he can work things
out using `sbt`.
Pat, could you clarify what you're asking for? I know it's been a request
for a long time to sort this out and I recommend we punt to a 14.2 release
to clear up any remaining issues.]
Thanks both!
On Wed
+1 (non-binding)
Chris
[OK] Download all staged artifacts under the url specified in the release vote
email into a directory we’ll now call download-dir.
[MINOR] Verify the signature is correct: Additional Apache tutorial on how to
verify downloads can be found here.
[OK] Check
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
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" :
Thank you so much for getting this out
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
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
Just fyi we have some bugs open on the latest RC, so anything related to
those is fine to check in.
Thanks
On Fri, Jun 26, 2020 at 10:26 AM Andrew Musselman wrote:
> Heads up we are cutting a release candidate today and as far as I know
> there is no work in progress, but to be clear
Andrew Musselman created MAHOUT-2109:
Summary: Add release notes to source bundle
Key: MAHOUT-2109
URL: https://issues.apache.org/jira/browse/MAHOUT-2109
Project: Mahout
Issue Type: Task
Heads up we are cutting a release candidate today and as far as I know
there is no work in progress, but to be clear please freeze any check-ins
this weekend and until 14.1 is out.
Thanks!
rawkintrevo closed pull request #384:
URL: https://github.com/apache/mahout/pull/384
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
Robert Gonciarz created MAHOUT-2098:
---
Summary: Release 0.14 mahout-mr to central repo
Key: MAHOUT-2098
URL: https://issues.apache.org/jira/browse/MAHOUT-2098
Project: Mahout
Issue Type
Andrew Palumbo created MAHOUT-2089:
--
Summary: generate sha-256 and sha-512 checksums for all release
artifacts
Key: MAHOUT-2089
URL: https://issues.apache.org/jira/browse/MAHOUT-2089
Project: Mahout
k I'l be out later. Have a quick minute.. Going to give you the weird hack
that I used to get the releases out. (I think that if we have Validate goal in
the `release-profile` somewhere, there would be no need for the hack.
Wow i really wish I'd just rewritten all of this in gradle rather
okay
but if my settings points to that machine then a release will go honking wrong
U had gitbox in your settings.xml?
I think maybe it's now.. I was using the GitHub repo before.
I'm not getting a response from it
Did you do add the servers from that pr to your settings.xml?
wish me luck
I'm trying out a release, can I go for it?
andrewpalumbo commented on a change in pull request #384: [MAHOUT-2076]: add a
/release directory with a skeleton settings.xml …
URL: https://github.com/apache/mahout/pull/384#discussion_r373771961
##
File path: release/_.m2_settings.xml
##
@@ -63,23 +63,23
Ahhh the release was deployed as a Snapshot.. sitll will look into structure.
FYI halfway through RC4, but i think there may be an issue. I had to make
local changes to get the root pom parsable, was attempting to validate it,
however it deployed artifacts, I will look through them if i can tonight, and
if I can not finish, will rollback the release.
before calling
Ok thanks, I'll try to give another shot now too. Testing right now, and will
push and try an RC agaian. But if it doesnt go through I'll have to leav it
for the morning. Soeey again..
Okay np will try in the morning
/assembly/bin.xml
index df2c58cd8..55d0cff69 100644
--- a/distribution/src/main/resources/assembly/bin.xml
+++ b/distribution/src/main/resources/assembly/bin.xml
@@ -113,13 +113,6 @@
755
755
-
-release
-dist/release
-true
... SUCCESS [ 1.370 s]
[INFO] - Mahout Spark CLI Drivers . SUCCESS [ 23.760 s]
[INFO] Mahout Release Package . SUCCESS [ 23.405 s]
[INFO]
[INFO
Yeah I did and got the same error; I'll see what changed and try to fix
Yeah I did and got the same error; I'll see what changed and try to fix
On Fri, Jan 31, 2020 at 16:52 Andy Palumbo - [mahout] [slack] <
0-14-0-rele...@mahout.mailclark.ai> wrote:
> Never saw that, unless I introduced it this morning when trying to roll
> back. Maybe clean out your .m2 cache
>
>
Never saw that, unless I introduced it this morning when trying to roll back.
Maybe clean out your .m2 cache
?
```INFO] [INFO] BUILD FAILURE
[INFO] [INFO]
[INFO] [INFO] Total time: 39.490 s
[INFO] [INFO] Finished at: 2020-01-31T16:48:39-08:00
[INFO] [INFO]
Hi Andy,
I am happy to read more about it. As Bertrand mentioned it's a common
consideration.
Tomek
On Mon, Jan 27, 2020 at 9:07 AM Bertrand Delacretaz
wrote:
> Hi,
>
> On Mon, Jan 27, 2020 at 12:53 AM Andrew Palumbo
> wrote:
> > ...Please let me know if a write-up of MailClark integration
Hi,
On Mon, Jan 27, 2020 at 12:53 AM Andrew Palumbo wrote:
> ...Please let me know if a write-up of MailClark integration would be
> useful...
I think so - making good use of Slack is a recurring question that you
seem to have tackled in a very constructive way.
-Bertrand
Hello All,
We have set up Mahout's slack space to forward directly to
dev@mahout.apache.org. We will now be able to plan publicly on slack. This a
bi-directional connection, all messages to dev@mahout.apache.org will show up
in Slack. No one will be left out of planning.
IRC, Slack,
FYI, all, since I pushed the (small) refactor through late at night, directory
structure will be as detailed here:
https://issues.apache.org/jira/browse/MAHOUT-2084#. PR
here:https://github.com/apache/mahout/pull/389/files sorry for the odd hours
and for having to push things through like
Hey all, FYI I started work on RC4 this morning. I'll be working on it later
today, but it may need a rollback. There was a small refactor that i pushed
through last night to adhere with some the asf release guidelines. I.e.
releasing all distribution artifacts into a single directory[1
andrewpalumbo commented on issue #390: MAHOUT-2085 Add scm tag for each pom.xml
per ASF release guidelines
URL: https://github.com/apache/mahout/pull/390#issuecomment-577783098
merging without review for RC4
andrewpalumbo merged pull request #390: MAHOUT-2085 Add scm tag for each
pom.xml per ASF release guidelines
URL: https://github.com/apache/mahout/pull/390
This is an automated message from the Apache Git Service.
To respond
andrewpalumbo opened a new pull request #390: MAHOUT-2085 Add scm tag for each
pom.xml per ASF release guidelines
URL: https://github.com/apache/mahout/pull/390
### Purpose of PR:
Please give a short description of what this PR is for.
Add SCM element to each POM per Apache
andrewpalumbo merged pull request #389: [MAHOUT-2084][MAHOUT-2083]: prevent
build from creating a default source release in $MAHOUT_HOME/target
URL: https://github.com/apache/mahout/pull/389
This is an automated message
andrewpalumbo commented on issue #389: [MAHOUT-2084][MAHOUT-2083]: prevent
build from creating a default source release in $MAHOUT_HOME/target
URL: https://github.com/apache/mahout/pull/389#issuecomment-577745367
Pushing this to master without review as part of RC4
Andrew Palumbo created MAHOUT-2085:
--
Summary: Add scm tag for each pom.xml per asf release Guidelines
Key: MAHOUT-2085
URL: https://issues.apache.org/jira/browse/MAHOUT-2085
Project: Mahout
I think i have most of it figured out over night.. I'm really looking forward
to getting away from this release we're almost there.
rawkintrevo [4:24 AM]
lol, like all of the releases
apalumbo [4:26 AM]
seriously full out release hell my war with maven will end
andrewpalumbo opened a new pull request #389: MAHOUT-2084: prevent build from
creating a default source release in $MAHOUT_HOME/target
URL: https://github.com/apache/mahout/pull/389
### Purpose of PR:
Please give a short description of what this PR is for.
MAHOUT-2084: prevent
andrewpalumbo merged pull request #388: [MAHOUT-2083][release] fix 14.1-RC3
release, rollback manually, reset to scala 2.11…
URL: https://github.com/apache/mahout/pull/388
This is an automated message from the Apache Git
andrewpalumbo commented on issue #388: [MAHOUT-2083][release] fix 14.1-RC3
release, rollback manually, reset to scala 2.11…
URL: https://github.com/apache/mahout/pull/388#issuecomment-577490967
Going to push this for RC4
andrewpalumbo opened a new pull request #388: [MAHOUT-2083][release] fix
14.1-RC3 release manually, reset to scala 2.11…
URL: https://github.com/apache/mahout/pull/388
…, fix mismatch versions causing failures on engine and core modules prepare
for RC4.
### Purpose of PR:
Please
Andrew Palumbo created MAHOUT-2083:
--
Summary: Release sources contain pom.XmlBackup and are mising
engine and hdfs submodules
Key: MAHOUT-2083
URL: https://issues.apache.org/jira/browse/MAHOUT-2083
apalumbo [3:35 PM]
```Downloading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout-core_2.12/14.1/mahout-core_2.12-14.1.pom
Downloaded:
to test I need the resolver location. What is the URL for the staged binary? Is
it on the Nexus or Sonatype?
I need Scala 2.11
by default:
```[INFO]
[INFO]
[INFO] Building Apache Mahout 14.1
[INFO]
[INFO]
[INFO] --- maven-release-plugin:2.5.3:perform (default-cli) @ mahout
figured out a my gpg signing issue. Working on cutting RC3 now.
No prob Andy, feel better soon; I am on a deadline and may need to skip
tomorrow too
Hey all I'm not going to be able to make tomorrows eeting due to a bad flu. I
can make next week, I'm not even sure that There has been a time set for
tomorrow. Otherwise please do try to capture some broad strokes - I have the
notes from last meeting. At some time we should just set up a
And @abybody else.
Oops forgot link..
https://docs.google.com/document/d/10oWUL890PsFc8Bhbnd10OxLN7ef9wGcEYhpg9-L1Fnc/edit?usp=drivesdk
https://docs.google.com/document/d/10oWUL890PsFc8Bhbnd10OxLN7ef9wGcEYhpg9-L1Fnc/edit?usp=drivesdk
Hey @akm and @all I started a gdoc for this week's meet.
Thanks @akm, @all the release issues are trivial now. Everything is ready to
release, and RC builds. I'm running on a Mac and just updated. It may just be
a question of restating the key-server there may have been some security
updates that locked down access to gpg keys. It's only
Thanks, Andrew, Turns out i have a pretty bad Respiratory infection..
so on top of everything else, that. I'm pretty shot. Ill try again tomorrow,
since I'm going to be sitting around doing nothing.
Okay I can work on this later in the week, hope you feel better soon
RC status update: I'm having an issue with what I think is my gpg2 key-server.
There was a MacOs update last week that may require new congratulations. So k
can't sign and deploy the artifacts to staging.
Have been sick and am feeling better but still need to go to Dr for
Antibiotics.
Hey @all I'm just getting over some kinda flu .. I should be able to cut a
release in the next couple of days.
Just FYI- still on it. Possibly tomorrow.
--andy
On Dec 22, 2019 11:19 PM, "Andy Palumbo - [mahout] [slack]"
<0-14-0-rele...@mahout.mailclark.ai> wrote:
Hey g
Hey @all I'm just getting over some kinda flu .. I should be able to cut a
release in the next couple of days.
Just FYI- still on it. Possibly tomorrow.
--andy
Happy new years all!
Happy new year all, we will vote in January
hey all - FYI - I've been under the weather and have been unable to get an RC
cut on the timeline that I'd hoped. I'll try to get it out in the next day or
so, and will wait to send the vote untill sometime after new years.
or LMK [ @Andrew Musselman](mailto:a...@apache.org) if you'd
0-rele...@mahout.mailclark.ai <0-14-0-rele...@mahout.mailclark.ai>
on behalf of Andy Palumbo - [mahout] [slack]
<0-14-0-rele...@mahout.mailclark.ai>
Sent: Monday, December 23, 2019 2:19 AM
To: 0-14-0-rele...@mahout.mailclark.ai <0-14-0-rele...@mahout.mailclark.ai>
Subject: Re: 0 14 0 Re
same here, you too
Hey guys i was trying but the holiday season got started early this year. Fam
in town etc.. I may not be able to cut rv3 until after Xmas. I don't figure any
idy wants to be testing right now anyi. Just fyi.
Happy holidays all!
I'll prob be back online btw. Xmas and new year.
1 - 100 of 1186 matches
Mail list logo
