Visit Azul.com Support

Azul Zulu Versioning and Naming Conventions

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

This section explains the naming convention and versioning schemes for Azul Zulu binary packages.

Versioning Scheme

For historical reasons, Azul Zulu releases use different versioning schemes for different major versions. For Azul Zulu 8 and earlier, the version consists of 4 numbers: XX.YY.0.BB, the third number is always "0". For Azul Zulu 11 and later, the version consists of 3 numbers: XX.YY.BB.

Note
 For each quarterly release, the release version is defined by the major version and minor version (first two numbers, XX.YY).
The build number (BB) may vary within a release.

As of April 2021 release, the Azul Zulu versions use the following scheme:

Azul Zulu Major Version Full Version Format

8 and earlier

XX.YY.0.BB

11 and later

XX.YY.BB

The following table explains the meaning of XX, YY, and BB.

XX

The major version.

YY

The minor version.

  • even numbers indicate a PSU release

  • odd numbers indicate a CPU release

BB

The build number.

  • even numbers indicate an SA bundle

  • odd numbers indicate a CA or NV bundle

  • BB ≤ 50 indicate regular Update bundles

  • 51 ≤ BB < 1000 indicate BPR (Bundled Patch Release) bundles

  • BB ≥ 1000 indicate FVB (Fix Verification Bundle) bundles

Note
 Based on building and testing results, the build number can be different within a release, typically grouping different platforms.

Versioning Examples

  • 8.54.0.21 - Azul Zulu 8, a CA bundle of a regular CPU release

  • 8.54.0.22 - Azul Zulu 8, a SA bundle of a regular PSU release

  • 8.54.0.56 - Azul Zulu 8, an SA bundle of a PSU-based bundled patch release (BPR)

  • 8.54.0.1018 - Azul Zulu 8, an SA fix verification bundle (FVB) for a PSU release

  • 11.48.22 - Azul Zulu 11, an SA bundle of a regular PSU release

  • 13.39.15 - Azul Zulu 13, an NV bundle of a regular CPU release

  • 15.32.54 - Azul Zulu 15, an SA bundle of a PSU-based bundled patch release (BPR)

  • 11.48.1004 - Azul Zulu 11, an SA fix verification bundle (FVB) for a PSU release

Bundle Name Convention

Azul Zulu uses a naming convention that encodes relevant information about a bundle into the bundle name. For example:

 
zulu15.31.14-sa-jre15.0.2.0.101-linux_musl_x64.tar.gz

The following table details most common components that make up a name of downloadable Azul Zulu package.

Bundle name part Description

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

Azul Zulu Version. See Versioning Scheme for details.

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

Distribution type (SA, CA, NV):

  • sa - subscriber availability

  • ca - community availability

  • nv - "non-verified" builds

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

Java functionality included in the bundle:

  • jdk - Java Development Kit

  • jre - Java Runtime Environment

  • hl - Headless version of a JDK or JRE (without GUI components)

  • fx-jdk - JDK with JavaFX support

  • fx-jre - JRE with JavaFX support

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

Java update version

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

OS family: linux, linux_musl, win, macosx, solaris, qnx

zulu15.29.14-sa-jdk15.0.2-linux_x64.tar.gz

CPU architecture: x64, i686, i386, amd64, aarch64, aarch32sf, aarch32hf, ppc64, ppc32hf, ppc32spe, mips32sf
Note
 Please note that Azul does not build bundles for all possible combinations of the values provided in the table above. Rather, you can use this table to understand what is included in a specific bundle.

There are additional optional suffixes that may appear in the name of a bundle. For example:

 
zulu8.54.0.22-sa-cp2-embvm-jre8.0.292-c2-linux_ppc64.tar.gz

Below is a description of the additional suffixes:

Suffix Description

ea

Early Access bundles.

Both SA and CA distributions may contain Early Access builds noted with -ea- in their filename. Early Access builds may not be TCK certified.

embvm

The bundle is built with the JAVASE_EMBEDDED option. Bundles with this suffix were discontinued in October 2021.

cp1, cp2, or cp3

One of the Java SE Embedded Compact profiles. Read more about compact profiles at https://foojay.io/pedia/compactprofiles/.

c2

Indicates that the bundle contains both Client and Server HotSpot JIT compilers. Bundles that don’t have this suffix contain only the Client compilers. This suffix can be present in bundles for the ARM 32-bit architecture.

criu

Bundles with the checkpoint/restore functionality.

cr

Bundles with the CRaM (Checkpoint / Restore at Main) functionality.

crac

Bundles with the CRaC (Coordinated Restore at Checkpoint) functionality.