The minimum would be: 1) refactor mrlegacy out of scala deps. This is done but held up. Anything to say Dmitriy? 2) build fixes for release. I heard a rumor that Suneel might be able to tackle that. 3) docs—might be good to guinea-pig the new CMS with git pubsub so we don’t have to do svn, not sure when that will be ready Anything else that has to be in?
Lots of good things in the offing but we could get into a quicker cycle with the release build fixed up. On Mar 17, 2015, at 9:13 AM, Shannon Quinn <squ...@gatech.edu> wrote: I think we need a better idea of what the release will contain, then we can start narrowing the range of possible release dates. If we take what Pat outlined, an April release might be somewhat ambitious but we probably wouldn't miss by much. On 3/17/15 11:51 AM, David Starina wrote: > Hi guys, > > Do you have any specific release date in mind? Guys at Bigtop are planning > an april release, is there any chance there will be a Hadoop 2.x compatible > Mahout release by then to be included with Bigtop? > > > > On Sunday, March 15, 2015, Pat Ferrel <p...@occamsmachete.com> wrote: > >> Lots of discussion off the record about doing a release but shouldn’t we >> plan this? >> >> What has to be in a release of Mahout 0.10? >> >> Seems like we could release as-is but it would be nice to have some of the >> already completed work that isn’t committed yet: >> * mrlegacy refactored out of scala, is it possible to get this in Dmitriy? >> >> One question is how to package, with which version of Spark. There is a >> bug in Spark 1.2.1 and I think in 1.2 (this is the big distro build) that >> requires any class that uses the JavaSerializer to set a specific SparkConf >> key/value to point to the guava jar on all workers. This only effects >> IndexedDatasets since they use Guava’s BiMap. Rumor has it that 1.3 fixes >> this but I haven’t tried it yet. >> >> So we are currently stuck on 1.1.1 but could document how to work around >> to use 1.2 for a user who want’s to build Mahout from scratch. A user >> source build on 1.3 may not require a work around. We seem to be good on >> hadoop 2.x, which in itself is a good reason to release since 0.9 was not. >> >> What else needs to be done: >> * rename module math-scala to core? >> * create the distribution build. Currently this does not publish the >> scaladocs and does not create artifacts for H2O or and Scala. >> * is H2O really in a form to publish? >> >> Docs >> * IMO we should name the Mahout Spark-Scala DSL and shell. More unique >> names are easier to find in searches. Maybe Suneel can polish off his >> sanskrit and suggest something. >> * we should be ready to do some work here to restructure the CMS since it >> is very 0.9 centric with Scala stuff almost an afterthought.
