12:15 PM
Subject:Re: Formalize a release candidate review process?
On Mon, May 23, 2016 at 11:34 AM, Niketan Pansare
wrote:
> +1 for formalizing the release candidate process. Please note: the point
9
> and 10 (i.e. performance suite) on 6-node cluster including XS (0.08 GB)
to
>
On Mon, May 23, 2016 at 11:34 AM, Niketan Pansare
wrote:
> +1 for formalizing the release candidate process. Please note: the point 9
> and 10 (i.e. performance suite) on 6-node cluster including XS (0.08 GB) to
> XL (800 GB) datasets takes 12-15 days. This estimate only includes
> following algo
is documentation to support their own release
> processes.
>
> Fred
>
> Luciano Resende ---05/21/2016 10:38:05 AM---+1, we should create a web
> page, about producing a release, where one section would be how to produc
>
> From: Luciano Resende
> To: "dev@systemml.
us.ibm.com
http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar
From: Frederick R Reiss/Almaden/IBM@IBMUS
To: dev@systemml.incubator.apache.org
Date: 05/23/2016 09:57 AM
Subject:Re: Formalize a release candidate review process?
+1 here too. A documented release
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 clai
+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
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 w
