OKL4 Versioning Policy

OKL4 software is versioned/named as follows:

• <product>-<version> for the initial release of a particular version of a software product

• Valid <product> names are okl4 and oklinux

• <product>-<version>-dev.x for an 'in development' version of a software product. When such a product is released, it will be released as <product>-<version>. I.e. the -dev.x suffix will be dropped.

• Released versions of our software may be supported or unmaintained. Supported versions may have bugfixes applied to them post release, or features backported to them.

  • When a bugfix is applied to <product>-<version>, the software version will change to <product>-<version>-patch.1.

  • When a bugfix is applied to <product>-<version>-patch.x, the software version will change to <product>-<version>-patch.<x+1>.

  • When a feature is backported to <product>-<version> or <product>-<version>-patch.x, the software version will change to <product>-<version++> where <version++> means:

    • Increment the minor version (i.e. number to right of the last dot in <version>) if the resulting version string is not already in use.

    • Otherwise suffix <version> with .1.

Examples:

• okl4 2.2 is in development

  • Software is versioned as okl4-2.2-dev.1, okl4-2.2-dev.2, ....

• okl4 2.2 is released

  • Software is versioned as okl4-2.2

• some bugfixes are added to okl4-2.2

  • New versions are okl4-2.2-patch.1, okl4-2.2-patch.2

• new feature is backported to okl4-2.2-patch.2

  • new version is okl4-2.2.1

• bugfix is applied to okl4-2.2-patch.2 and okl4-2.2.1

  • new versions are okl4-2.2-patch.3 and okl4-2.2.1-patch.1