I wouldn’t talk about 1.0 or the next release at all. We could say that it is our intention to have frequent releases or something like that, if only to track Spark or distro updates. The question is, what drives a release? Making it easy for users to use seems important to me. So having everything in their distribution just work together. This would assume that whatever is ready will be in the release but it is timed for the convenience of users. This is a non-feature driven model more like a distro driven schedule (BigTop included).
As far as #3 has anyone signed up for that? It means creating a new module and working through dependencies. Either replacing the use of something in mrlegacy or moving it to mahout-hadoop. The uses would be in math-scala or spark. On Mar 24, 2015, at 11:36 AM, Dmitriy Lyubimov <[email protected]> wrote: On Tue, Mar 24, 2015 at 11:21 AM, Andrew Musselman < [email protected]> wrote: > Summary of the call; please chime in with any corrections or > clarifications: > > (1) Support Lucene 5, Hadoop 2, Java 7, Spark 1.1 & 1.3 > (2) Ensure build is solid, add Scaladocs in poms and in Jenkins > (3) Factor mr-legacy into "mahout-hadoop" module > (4) Target 0.10.0 release for mid-April(for inclusion in BigTop release, > and for timing with ApacheCon), 0.10.1 for March, 1.0 for June > I am a bit confused. 0.10.1 perhaps for may and 0.11.0 for June-July? > (5) Maintain online docs, find a place for Scaladocs through infra > (6) One or two blog posts in flight; can publish on MapR blog and AWS blog > > Thanks to all for joining; we'll have another this weekend and/or next as > needed. > > Best > Andrew > > On Tue, Mar 24, 2015 at 11:14 AM, Suneel Marthi <[email protected]> > wrote: > >> Thanks for taking care of this Stevo. Fyi, we r targeting April 10 for > next >> release date. So it would be great if this could get in for the release. >> Dmitiry, what do u think about this? >> >> On Tue, Mar 24, 2015 at 2:03 PM, Stevo Slavić <[email protected]> wrote: >> >>> Hello Suneel, >>> >>> Thanks for special invite, unfortunately I cannot join today. >>> I've created https://issues.apache.org/jira/browse/MAHOUT-1654 for >>> tracking migration to sbt, and I'll work on it. >>> >>> If I'm not mistaken Ted expressed concerns in past of using anything > but >>> Maven, for all the good sides of Maven, like sticking to conventions. I >>> agreed and like Maven for same reasons. Now with Scala modules in >> project, >>> IMO we have to migrate to SBT, and try to stick to conventions as much > as >>> possible, not make build hacky. That's possible, requires discipline > but >>> has benefits as well, I'm successfully using SBT in several projects, >> with >>> clear and concise build scripts. >>> >>> Kind regards, >>> Stevo Slavic. >>> >>>> >>>> On Tue, Mar 24, 2015 at 11:47 AM, Stevo Slavić <[email protected]> >> wrote: >>>> >>>>> We should consider migrating entire project from Maven to SBT, since >>>>> project includes several Scala modules, for them to be usable to >>>>> community >>>>> IMO it's pretty much expected if not a must to publish them across >>>>> current >>>>> Scala binary versions, 2.10 and 2.11, and Maven is simply not up to >> that >>>>> task. >>>>> >>>>> Kind regards, >>>>> Stevo Slavic. >>>>> >>>>> On Tue, Mar 24, 2015 at 4:36 PM, Pat Ferrel <[email protected]> >>>>> wrote: >>>>> >>>>>> Andrew are you keeper of the agenda? >>>>>> >>>>>> I only have the first hour so my $0.02 worth. >>>>>> 1) Agree with Suneel that one top goal should be a Hadoop 2, Java > 7, >>>>>> upgraded libs version of mrlegacy because at this point no Mahout >>>>> release >>>>>> runs on the big distros. >>>>>> 2) Refactor of mrlegacy to remove it as a dependency of the scala >>>>>> environment >>>>>> 3) can we hand out docs to volunteers? This may mostly be done but > I >>>>> think >>>>>> Andy would know better. I’ll take legacy and scala recommender > stuff >>>>> and an >>>>>> example of writing an app that uses Mahout as a lib. >>>>>> 4) get a volunteer to do whatever is required to perform the > release >>>>>> (pending the vote) and any necessary build changes to get there >>>>> (Suneel?) >>>>>> >>>>>> On Mar 23, 2015, at 2:21 PM, Andrew Musselman < >>>>> [email protected]> >>>>>> wrote: >>>>>> >>>>>> Moving an hour later so more people can attend; so 10 a.m. to noon >>>>> Pacific. >>>>>> >>>>>> On Mon, Mar 23, 2015 at 1:19 PM, Andrew Musselman < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> We're splitting the difference so people in Europe can attend.. >>>>>>> >>>>>>> On Mon, Mar 23, 2015 at 1:15 PM, Saikat Kanjilal < >>>>> [email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Me2 and cant attend during those hours, thought I'd ask is it >>>>> completely >>>>>>>> out of the question to do it during evenings pacific time? >>>>>>>> >>>>>>>>> Date: Mon, 23 Mar 2015 16:01:50 -0400 >>>>>>>>> From: [email protected] >>>>>>>>> To: [email protected] >>>>>>>>> Subject: Re: 0.10 release Hangout >>>>>>>>> >>>>>>>>> Will be teaching until 9:30 PT, at which point I have another >>>>> meeting >>>>>>>>> until 11. Would love to get a summary of the meeting; also > happy >> to >>>>>> help >>>>>>>>> with some of the tasks. >>>>>>>>> >>>>>>>>> Shannon >>>>>>>>> >>>>>>>>> On 3/23/15 3:56 PM, Andrew Musselman wrote: >>>>>>>>>> We'll be getting on a Google Hangout tomorrow, Tuesday, from >> 9-11 >>>>> a.m. >>>>>>>>>> Pacific, to work through open questions for what should be in >> the >>>>>>>> release, >>>>>>>>>> go through Jira, and do some delegation of tasks. >>>>>>>>>> >>>>>>>>>> Here's the Hangout URL >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >> > https://plus.google.com/hangouts/_/calendar/YW5kcmV3Lm11c3NlbG1hbkBnbWFpbC5jb20.glvu1gfv3kvj5241n9bsg3clrc >>>>>>>>>> >>>>>>>>>> See you then! >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >
