systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [DISCUSS] SystemML with Spark 2.0 support and roadmap
Date Thu, 25 Aug 2016 01:05:49 GMT
I think this is a great idea so that we can simplify the official release and reduce confusion
for potential users.  Certainly we can still retain the potential to build the extra artifacts
locally, just like Spark current does.

I would also like to suggest that we move away from the current Standalone package that is
designed to be used with Java, and instead move to simply using Spark in local mode for all
"standalone" applications. Since running Spark locally on a laptop consists of simply downloading
a release binary and running it, without any installation, I think this is a much cleaner
way now. This would allow us to immediately move to the goal of only releasing a single JAR
file, as that same JAR file could be used in Spark locally, Spark on a cluster, and Hadoop
on a cluster.  Then we could just release the single JAR file and a folder of scripts as our
official release. All other special artifacts could be kept as "download and build" artifacts.


Mike Dusenberry

Sent from my iPhone.

> On Aug 23, 2016, at 5:22 PM, Luciano Resende <> wrote:
> On Tue, Aug 23, 2016 at 3:51 PM, Deron Eriksson <>
> wrote:
>> To simplify release candidate validation, I would like to propose that the
>> distribution profile only builds the following 7 (out of the current
>> included 10) artifacts:
>> systemml-0.11.0-incubating-SNAPSHOT-javadoc.jar
>> systemml-0.11.0-incubating-SNAPSHOT-sources.jar
>> systemml-0.11.0-incubating-SNAPSHOT-src.tar.gz
>> systemml-0.11.0-incubating-SNAPSHOT-standalone.tar.gz (rename w/o
>> "-standalone")
>> (rename w/o
>> "-standalone")
>> systemml-0.11.0-incubating-SNAPSHOT.jar
>> The following could still be built using maven profiles but would not be in
>> the distribution profile:
>> systemml-0.11.0-incubating-SNAPSHOT-standalone.jar
>> systemml-0.11.0-incubating-SNAPSHOT.tar.gz (also rename)
>> (also rename)
>> This would decrease the number of our artifacts by 30% which means that we
>> can validate the release faster, and the release candidate will also be
>> more likely to pass external validation/voting.
>> Deron
> +1
> -- 
> Luciano Resende

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message