Graal CE releases are available in https://github.com/graalvm/graalvm-ce-builds/releases and use the following naming convention:

graalvm-ce-javajava major version-os-arch-graal version.tar.gz

Facts

• Mandrel doesn't need to follow a similar convention
• Mandrel is being built using upstream OpenJDK instead of labs-OpenJDK
• Mandrel (like Graal) is sensitive to OpenJDK changes (thus its builds are tightly coupled to the OpenJDK version)

Proposal A

mandrel-javajava major version-os-arch-mandrel version.tar.gz

e.g. mandrel-java11-linux-amd64-20.1.3.2.tar.gz (see #39 for versioning)

Proposal B

mandrel-os-arch-mandrel version.tar.gz

e.g. mandrel-linux-amd64-20.1.3.2.tar.gz (see #39 for versioning)

If Mandrel is going to support only java 11 for the foreseeable feature there is no need to add java11 in the releases.

Proposal C

mandrel-javajava major.minor.patch.build version-os-arch-mandrel version.tar.gz

e.g. mandrel-java11.0.8.4-linux-amd64-20.1.3.2.tar.gz (see #39 for versioning)

Since Mandrel is tightly coupled to OpenJDK we might want to make the OpenJDK version visible in the releases. Keep in mind though that this info can be easily obtained by running java --version or native-image --version after extracting the tarball. I find this naming of great value if we plan to release tarballs containing only the Mandrel bits so that users could untar them and install alongside an existing OpenJDK installation.