For now, we should document every artifacts being created in release doc
(and/or website), which can be updated when artifacts get reduced.
-Arvind
From: Acs S <ac...@yahoo.com.INVALID>
To: "dev@systemml.incubator.apache.org" <dev@systemml.incubator.apache.org>
Sent: Monday, October 31, 2016 9:13 PM
Subject: Re: SystemML 0.11.0-incubating RC4 feedback
For some reason, I got an impression that artifacts reduction was completed
earlier, but apparently its not.We are trying to reduce number of artifacts to
avoid confusion to users.This is an issue from earlier releases as well, not
being introduced as a part of SystemML 0.11 release.
We can address it immediately after SystemML 0.11 goes out. We should not mark
this as a blocking issue for SystemML 0.11.
-Arvind
From: Luciano Resende <luckbr1...@gmail.com>
To: dev@systemml.incubator.apache.org
Sent: Monday, October 31, 2016 3:48 PM
Subject: Re: SystemML 0.11.0-incubating RC4 feedback
On Mon, Oct 31, 2016 at 2:11 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:
> Also, to quote Justin Mclean:
> "It not clear to me what exactly is the release artefacts here, for
> instance why does this directory include jars? Can you please clarify."
>
> From this response, I think it is clear that our large number of artifacts
> is causing confusion. We can in part reduce this confusion by dropping our
> number of released artifacts, as addressed by
> https://issues.apache.org/jira/browse/SYSTEMML-926.
>
> Deron
>
>
>
Ok, I have marked the jira above as blocker for 0.11 release. Could you
guys please make sure all other remaining blocking issues are marked as so
for 0.11 release, so it makes it easier for myself to check when the next
RC should be created.
Thanks
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
