systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frederick R Reiss" <>
Subject Re: Formalize a release candidate review process?
Date Mon, 23 May 2016 16:34:43 GMT

+1 here too. A documented release process is a very good idea. Having a
written checklist will make it easier to delegate these tasks to volunteers
who want to help out with the project. It will also build confidence among
potential users, since we can point to exactly what testing has been done
on each release. And any vendors who are thinking of bundling SystemML with
their products will want this documentation to support their own release


From:	Luciano Resende <>
To:	""
Date:	05/21/2016 10:38 AM
Subject:	Re: Formalize a release candidate review process?

+1, we should create a web page, about producing a release, where one
section would be how to produce a release candidate, and another session
would be thse items below with a bit more info on how ro execute them...
And then people could claim these or respond to the vote with the things
they have tested.

Btw, for the build ones, we should recommend building with an empty maven

On Saturday, May 21, 2016, Deron Eriksson <> wrote:

> Hi,
> It might be nice to formalize what needs to be done when reviewing a
> release candidate. I don't mean this as something that would add
> bureaucracy that would slow us down. Rather, it would be nice to have
> something as simple as a basic checklist of items that we could volunteer
> to check. That way, we could avoid potentially duplicating effort, which
> would speed us up, and we could avoid potentially missing some critical
> checks, which would help validate the integrity of our releases.
> Some potential items to check:
> 1) Entire test suite should pass on OS X, Windows, and Linux.
> 2) All artifacts and accompanying checksums are present (see

> )
> 3) All artifacts containing SystemML classes can execute a 'hello world'
> example
> 4) LICENSE and NOTICE files for all the artifacts have been checked
> 5) SystemML runs algorithms locally in standalone single-node
> 5) SystemML runs algorithms on local Hadoop (hadoop jar ...)
> 6) SystemML runs algorithms on local Spark (spark-submit ...)
> 7) SystemML runs algorithms on a Hadoop cluster
> 8) SystemML runs algorithms on a Spark cluster
> 9) SystemML performance suite has been run on a Hadoop cluster
> 10) SystemML performance suite has been run on a Spark cluster
> Would this be too many things to check or too few? Are there any critical
> items missing?
> Deron

Sent from my Mobile device

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message