Support and Documentation

Version numbering format

For the 3.3 line of releases, version numbering for releases and components are reflected in the Maven bill of materials POM, also referred to as the BOM.

The release number is expressed in a major.minor.patch format, where major.minor identifies the release line and patch identifies the incremental build. In the following BOM, the release is 3.3.22, where 3.3 is the major.minor version and 22 is the patch identifier. The 3.3.22 release can also be expressed as 3.3 - Patch Release #22. Patch numbers are usually incremented by one from one release build to the next.

<parent>
    <groupId>com.psddev</groupId>
    <artifactId>brightspot-grandparent</artifactId>
    <version>3.3.22</version>
    <relativePath>../grandparent/pom.xml</relativePath>
</parent>

Each component (Dari, Brightspot, plugins, etc.) in the release has its own unique version number, all managed by the BOM. For example, this snippet from the BOM shows the version number for the conversation plugin.

<!--  conversation  -->
<dependency>
    <groupId>com.psddev</groupId>
    <artifactId>conversation</artifactId>
    <version>1.1.49-0517a7</version>
</dependency>

Component versions use the following format:

<major>.<minor>.<# of commits>-<commit hash>

For example, the conversation plugin version is 1.1.49-0517a7, where:

  • major version: 1

  • minor version: 1

  • # of commits (patch version): 49

  • commit hash: 0517a7

With a BOM, you do not have to specify version numbers for Brightspot-related dependencies. For more information, see Upgrading your version of Brightspot.

As an alternative to the BOM, you can view your version within Brightspot. For details, see What version of Brightspot do I have?.