<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Hi all,<br>
<br>
As we are approaching the end of the month the Mandrel team would
like to push out a new release and would appreciate your input on
the versioning scheme before that.<br>
</p>
<p>If we don't hear back soon we will probably proceed with the most
safe approach of using 20.1.0.1 as the version number for this
release.<br>
</p>
<p>Thanks,<br>
Foivos<br>
</p>
<div class="moz-cite-prefix">On 16/07/2020 23:44, Oleg Šelajev
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B0C5C060-FCD3-4298-A38C-89915A9DAC7A@ORACLE.COM">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Foivos,
<div class=""><br class="">
</div>
<div class="">we've updated the page with the roadmap, not to list
outdated information <a
href="https://www.graalvm.org/docs/release-notes/version-roadmap/"
class="" moz-do-not-send="true">https://www.graalvm.org/docs/release-notes/version-roadmap/</a></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Regarding the versioning question, we're discussing
this and will come back with thoughts. </div>
<div class=""><br class="">
</div>
<div class="">Thanks, </div>
<div class="">Oleg</div>
<div class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 16 Jul 2020, at 16:11, Foivos Zakkak <<a
href="mailto:fzakkak@redhat.com" class=""
moz-do-not-send="true">fzakkak@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hello all,<br class="">
<br class="">
I would like to bring to your attention an issue that
came up regarding<br class="">
the versioning scheme of Mandrel.<br class="">
<br class="">
Based on the graalvm roadmap [1] (which appears to be
outdated per [2])<br class="">
the Mandrel team initially decided to follow the
following version scheme:<br class="">
<br class="">
YY.X.Z.W where YY.X.Z would be the graalVM CE version
that Mandrel<br class="">
YY.X.Z.W is based on, and W would be an incremental
number for patches<br class="">
on the Mandrel side (including backports, bug fixes,
features, etc.).<br class="">
So 20.1.0.3 would be based on GraalVM 20.1.0 CE,
20.1.1.2 would be based<br class="">
on GraalVM 20.1.1 CE etc.<br class="">
<br class="">
However, according to the new roadmap [2] there will be
no YY.0.1,<br class="">
YY.1.1, and YY.2.1 CE releases only YY.0 YY.1 YY.2 and
YY.3.0-3.<br class="">
In the old roadmap [1], YY.Z.1 releases were meant to be
CPU releases<br class="">
(aligned with openJDK CPU releases), but in the new
roadmap CPU patches<br class="">
will appear in the next Minor Feature Release (e.g. in
20.2 instead of<br class="">
20.1.1).<br class="">
<br class="">
The mandrel team would like to keep its CPU releases as
close as<br class="">
possible to the openJDK CPU releases, thus it would like
to stay closer<br class="">
to the old roadmap.<br class="">
As a result a new mandrel release is expected to come
out with each<br class="">
openJDK CPU release (or a few days later).<br class="">
This mandrel release will be based on the latest mandrel
release (which<br class="">
will probably be aligned with the latest GraalVM CE
release).<br class="">
<br class="">
So at this point we have a CPU release candidate that is
based on<br class="">
Mandrel 20.1.0.0 which in turn is based on GraalVM
20.1.0 CE.<br class="">
The question is how should this Mandrel release be
tagged? 20.1.0.1 or<br class="">
20.1.1.0 or something else?<br class="">
<br class="">
20.1.0.1 makes clear that the release is based on
GraalVM 20.1.0 CE and<br class="">
there is no chance of anyone relating it to GraalVM
20.1.1 EE.<br class="">
On the other hand if we have multiple releases e.g.,
20.1.0.0, 20.1.0.1,<br class="">
20.1.0.2, and 20.1.0.3 there is no way to tell which of
them arre CPU<br class="">
releases.<br class="">
<br class="">
20.1.1.0 makes clear that this is a CPU release but
people might be<br class="">
confused regarding its relationship to GraalVM 20.1.1
EE.<br class="">
Another issue with this scheme is that Mandrel will
probably release<br class="">
20.3.1 before GraalVM CE 20.3.1 so there might be some
confusion there<br class="">
as well.<br class="">
<br class="">
What are your thoughts?<br class="">
<br class="">
Regards,<br class="">
Foivos<br class="">
<br class="">
[1] <a
href="https://www.graalvm.org/docs/release-notes/version-roadmap/"
class="" moz-do-not-send="true">https://www.graalvm.org/docs/release-notes/version-roadmap/</a><br
class="">
[2] <a
href="https://graalvm.slack.com/archives/CNBFR78F9/p1594804615255100"
class="" moz-do-not-send="true">https://graalvm.slack.com/archives/CNBFR78F9/p1594804615255100</a><br
class="">
<br class="">
<br class="">
_______________________________________________<br
class="">
GraalVM-Dev mailing list<br class="">
<a href="mailto:GraalVM-Dev@oss.oracle.com" class=""
moz-do-not-send="true">GraalVM-Dev@oss.oracle.com</a><br
class="">
<a class="moz-txt-link-freetext" href="https://oss.oracle.com/mailman/listinfo/graalvm-dev">https://oss.oracle.com/mailman/listinfo/graalvm-dev</a></div>
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Foivos Zakkak
Senior Software Engineer, R&D Middleware
Red Hat
7B40 69D9 29BA AE91 C0B3 220A 0846 BFD1 03F0 4EA1</pre>
</body>
</html>