A word of warning about making decisions off-list and without a permanent
record on the mailing list.
I will likely be available, but may not be. I am happy with whatever the
consensus is (with a tilt towards frequent releases), but would like to see
most of the decision process on the list.
[
https://issues.apache.org/jira/browse/MAHOUT-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAHOUT-1680 started by Stevo Slavic.
Rename project release artifact names to be prefixed with 'apache-mahout-*
Not sure if I will be able to attend.
IMO, in major.minor.patch semantic versioning scheme (which I believe we're
applying and want to adhere to), there is no frequency dimension, there's
just scope dimension. There is nothing in versioning scheme preventing one
to release even major version
On Tue, Apr 14, 2015 at 3:11 AM, Ted Dunning ted.dunn...@gmail.com wrote:
On Tue, Apr 14, 2015 at 8:49 AM, Stevo Slavić ssla...@gmail.com wrote:
I'm not sure but I doubt there's anything in Apache way of doing things,
that's preventing us from having both 0.10.1 and 0.11.0 releases planned
[
https://issues.apache.org/jira/browse/MAHOUT-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAHOUT-1681 started by Stevo Slavic.
Rename module - 'mahout-math-scala' to 'mahout-samsara'
On Tue, Apr 14, 2015 at 8:49 AM, Stevo Slavić ssla...@gmail.com wrote:
I'm not sure but I doubt there's anything in Apache way of doing things,
that's preventing us from having both 0.10.1 and 0.11.0 releases planned
and worked on in parallel with dedicated branches e.g. master for next
On Tue, Apr 14, 2015 at 3:48 AM, Stevo Slavić ssla...@gmail.com wrote:
Btw, I volunteer to create a 0.10.x branch and any needed changes in build
scripts to make branch releasable. In JIRA I guess these days anyone
(including me) can create 0.10.1 version and define scope for it, assign
Btw, I volunteer to create a 0.10.x branch and any needed changes in build
scripts to make branch releasable. In JIRA I guess these days anyone
(including me) can create 0.10.1 version and define scope for it, assign
issues.
On Tue, Apr 14, 2015 at 9:14 AM, Suneel Marthi smar...@apache.org wrote:
See https://builds.apache.org/job/Mahout-Quality/3118/changes
Changes:
[sslavic] MAHOUT-1680: Renamed mahout-distribution to apache-mahout-distribution
--
[...truncated 1797 lines...]
0 =
[
https://issues.apache.org/jira/browse/MAHOUT-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493858#comment-14493858
]
Hudson commented on MAHOUT-1680:
FAILURE: Integrated in Mahout-Quality #3118 (See
[
https://issues.apache.org/jira/browse/MAHOUT-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493914#comment-14493914
]
Stevo Slavic commented on MAHOUT-1680:
--
Build was stuck on h2o. Next build passed
[
https://issues.apache.org/jira/browse/MAHOUT-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAHOUT-1680 stopped by Stevo Slavic.
Rename project release artifact names to be prefixed with 'apache-mahout-*
[
https://issues.apache.org/jira/browse/MAHOUT-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stevo Slavic resolved MAHOUT-1680.
--
Resolution: Fixed
Rename project release artifact names to be prefixed with 'apache-mahout-*
[
https://issues.apache.org/jira/browse/MAHOUT-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAHOUT-1681 stopped by Stevo Slavic.
Rename module - 'mahout-math-scala' to 'mahout-samsara'
See https://builds.apache.org/job/Mahout-Quality/3119/changes
[
https://issues.apache.org/jira/browse/MAHOUT-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493873#comment-14493873
]
Hudson commented on MAHOUT-1681:
SUCCESS: Integrated in Mahout-Quality #3119 (See
we had a hangout with Dmitriy, Suneel, Andy, Stevo, Pat
We discussed the release strategy for Mahout and would like to propose:
Mahout 0.10.1 is a new branch that will include some changes to the base linear
algebra implementations, which are source compatible with 0.10.
Mahout 0.11 will be the
Will 0.11 pull in all new features and bug fixes from 0.10.1, and then
have changes that are required for Spark 1.3?
Sounds good to me.
On Tuesday, April 14, 2015, Pat Ferrel p...@occamsmachete.com wrote:
we had a hangout with Dmitriy, Suneel, Andy, Stevo, Pat
We discussed the release
you need to check task log.
On Tue, Apr 14, 2015 at 11:26 AM, Pat Ferrel p...@occamsmachete.com wrote:
Running cooccurrence calc on Spark 1.1.1 Hadoop 2.4 with Yarn
This isn’t a problem in our code is it? I’ve never run into a
TaskResultLost, not sure what can cause that.
TaskResultLost
See https://builds.apache.org/job/Mahout-Examples-Cluster-Reuters-II/1158/
Thanks Stevo.
On Tue, Apr 14, 2015 at 8:14 PM, Stevo Slavić ssla...@gmail.com wrote:
Hello team,
mahout-0.10.x branch has been created for work on 0.10.1 release and any
future 0.10.x releases.
Project JIRA has 0.10.1 version defined so issues can be target to be fixed
for 0.10.1 release.
Hello team,
mahout-0.10.x branch has been created for work on 0.10.1 release and any
future 0.10.x releases.
Project JIRA has 0.10.1 version defined so issues can be target to be fixed
for 0.10.1 release.
Somebody with privileges has to cover mahout-0.10.x branch with Jenkins
build jobs.
thanks. great to know
On Tue, Apr 14, 2015 at 5:14 PM, Stevo Slavić ssla...@gmail.com wrote:
Hello team,
mahout-0.10.x branch has been created for work on 0.10.1 release and any
future 0.10.x releases.
Project JIRA has 0.10.1 version defined so issues can be target to be fixed
for 0.10.1
[
https://issues.apache.org/jira/browse/MAHOUT-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stevo Slavic resolved MAHOUT-1681.
--
Resolution: Won't Fix
Reverted commit, resolving as won't fix.
Rename module -
[
https://issues.apache.org/jira/browse/MAHOUT-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stevo Slavic reopened MAHOUT-1681:
--
Reopening (see discussion at
Stronly agree
On Tuesday, April 14, 2015, Suneel Marthi suneel.mar...@gmail.com wrote:
... and we need to doing a hangout at more regular frequencies, every
Tuesday (or whatever works) at 1pm ET (again whatever works here for most).
This is something that projects like Drilll have been doing
See https://builds.apache.org/job/Mahout-Quality/3121/changes
Allen McIntosh created MAHOUT-1690:
--
Summary: CLONE - Some vector dumper flags are expecting arguments.
Key: MAHOUT-1690
URL: https://issues.apache.org/jira/browse/MAHOUT-1690
Project: Mahout
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen McIntosh updated MAHOUT-1690:
---
Fix Version/s: (was: 0.8)
CLONE - Some vector dumper flags are expecting arguments.
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen McIntosh updated MAHOUT-1690:
---
Affects Version/s: (was: 0.6)
0.10.0
CLONE - Some vector dumper
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen McIntosh updated MAHOUT-1690:
---
Description: MAHOUT-993 seems to be back. In particular, the
--sortVectors/-sort option
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi reassigned MAHOUT-1690:
-
Assignee: Suneel Marthi (was: Sebastian Schelter)
CLONE - Some vector dumper flags
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495077#comment-14495077
]
Suneel Marthi commented on MAHOUT-1690:
---
Will look at this when I have time. I
[
https://issues.apache.org/jira/browse/MAHOUT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi updated MAHOUT-1690:
--
Fix Version/s: 0.10.1
CLONE - Some vector dumper flags are expecting arguments.
See https://builds.apache.org/job/Mahout-Quality/3120/
--
[...truncated 1795 lines...]
{
0 = {0:-0.2025553055680292,1:-0.33048532362095073,2:0.8679661611426595}
1 = {0:-0.35360441819665717,1:-0.8516338166977458,2:-0.37902461833381257}
2 =
... and we need to doing a hangout at more regular frequencies, every
Tuesday (or whatever works) at 1pm ET (again whatever works here for most).
This is something that projects like Drilll have been doing for a few years
now.
On Tue, Apr 14, 2015 at 1:57 PM, Pat Ferrel p...@occamsmachete.com
Running cooccurrence calc on Spark 1.1.1 Hadoop 2.4 with Yarn
This isn’t a problem in our code is it? I’ve never run into a TaskResultLost,
not sure what can cause that.
TaskResultLost (result lost from block manager)
nivea.m https://gd-a.slack.com/team/nivea.m[11:01 AM]
collect at
37 matches
Mail list logo
