great thanks for the perspectives.
ad 1) renaming master to main is a fine proposal for more inclusive
naming. Let's separate it from the release discussion though as its
purely related to our infrastructure.
ad 2) for the post-2.1 release we can also discuss directly going to
SystemDS 3.0 to indicate this change of external behavior, and align
with the hadoop and spark versions.
ad 3) do we have any volunteers for taking over the responsibility of
the release manager for SystemDS 2.1?
Regards,
Matthias
On 2/8/2021 3:59 PM, Mark Dokter wrote:
On 08/02/2021 15:45, arnab phani wrote:
+1
I think the best order will be first to move to Java 11, make the
system stable, and then switch to Spark 3.
+1
If Spark 2.x works with Java 11 (I didn't check), then this sounds like
a good plan. Otherwise it's all at once :-P
While we're at breaking changes: I heard master branch renames are quite
fashionable these days (e.g., master -> main).
Regards,
Arnab..
Regards,
Mark
On Mon, Feb 8, 2021 at 3:38 PM Baunsgaard, Sebastian
<[email protected]> wrote:
+1
The only question is in what order to upgrade or all at once?
________________________________
From: Matthias Boehm <[email protected]>
Sent: Monday, February 8, 2021 1:21:55 PM
To: [email protected]
Subject: SystemDS 2.1 (Spark 2.x and Java 8)
Hi all,
Spark 3 is out since June 2020, and we see an increasing move from Java
8 to Java 11. I think it would be good to have one last release before
we make these backwards-incompatible changes though. What do you think
about releasing SystemDS 2.1 around end of March and then making the
switch to Spark 3 (and Hadoop 3), and Java 11?
Regards,
Matthias
