Re: Building releases now that we have branches

On Fri, Jan 20, 2017 at 4:51 PM, wrote: > Yes, this commit probably shouldn't have gone to master... > Can one of the commiters revert it? > > I would leave for the Release manager to revert it > Now, for the RC2, we will probably need to make the RC based on the commit >>

Building releases now that we have branches

I just saw a commit into master : [maven-release-plugin] prepare release v0.12.0-incubating-rc2” --tag Please be very careful with what we are trying to do. After 0.12 RC, we have moved the development of 0.12 wich is based on Spark 1.6.x to a 0.12 branch, but the commit info above makes me think

Scala API/DSL alignment

Hi all, I started writing a short doc that summarized our current approaches to interacting with SystemML in Scala: https://docs.google.com/document/d/1ntdfmSBB83zdcWZl2iv4yMsrA3ZHDM-mzX5lMfFpfeo/edit?usp=sharing The doc contains currently implemented features as well as considerations for

Build failed in Jenkins: SystemML-DailyTest #760

See -- [...truncated 9600 lines...] 17/01/20 03:49:05 INFO scheduler.DAGScheduler: running: Set() 17/01/20 03:49:05 INFO scheduler.DAGScheduler: waiting: Set(ResultStage 243) 17/01/20