Azul Terms Glossary

Here are definitions of commonly used terms and acronyms used by Azul. 

This glossary is a work in progress. Please don't hesitate to let us know of terms you come across in our software or documentation that you'd like us to define here.

Most of these terms are used in the context of Azul Zulu Builds of OpenJDK. Where they are used for Azul Zulu Prime JDK or other Azul products the same definitions apply unless otherwise specified. 

  • BPR - Bundled Patch Release
    • Bundled Patch Releases are created when a customer needs a bug fix or enhancement released to them before the next scheduled Update Release.
    • See also: FVB, GA, respin.
  • CA - Community Access
  • CPU - Critical Patch Update
  • FVB - Fix Verification Bundle
    • Fix Verification Bundles are created when we are giving a bundle to a customer to have them try a possible fix or enhancement to verify it works as intended before it is GA (Generally Available) released.
    • See also: BPR, GA.
  • GA - Generally Available
    • Refers to products made generally available to the community or supported customers. See also: BPR, FVB.
  • NV - Non-Verified
  • PSU - Patch Set Update 
  • Respin
    • Sometimes there are late-arriving changes from OpenJDK that come too late to be included in the scheduled Release, or changes are discovered to be necessary after a Release has already been published. We refer to these situations and their new builds as a "respin". This is not an "official term", but it is one you may see us use for updates to scheduled Releases. 
    • Clarification with regard to BPR (Bundled Patch Release): A respin is an update to a scheduled Mainline or Update Release. A BPR is an update containing fixes or enhancements needed by one or more customers before the next scheduled Update Release. The Zulu version "build number" will be <50 for Feature Releases, Update Releases, and any "respins" of them. A Zulu version "build number" between 50 and 1000 is used for BPRs. 
    • See also: BPR
  • SA - Subscriber Access

Add Comment



Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful