You're seeing a degraded version of this site because the site's layout requires JavaScript. Please activate JavaScript and reload this page.

Version Number Conventions

By Chris Spiel, December 17th, 2012

Version Numbering

Enblend and Enfuse program versions adhere to a strict scheme. Well, at least the developers try hard to stick to it! The unambiguous versioning simplifies the developers' task of tracking down bugs and allows users for exact matching the binaries with their documentation.

Branched Development

Enblend and Enfuse are developed in two so-called branches: a development branch (called "default" in the Mercurial repository) and a stable or maintenance branch (called "stable-#-#", where the sharp-signs represent the major and minor version numbers when the respective stable-branch was forked off).

Development Branch
  • Double index version numbers: MAJOR.MINOR
  • Intermediate, un-released versions have a twelve-digit hexadecimal code attached, like e.g. -7ae330dc530e. Final, released versions always lack this id!
  • Release candidates at the very late stage of every development cycle have an -RC# attached to the double index version numbers, where "#" is the number of the release candidate.
Stable Branch
  • Triple index version numbers: MAJOR.MINOR.PATCHLEVEL
  • Intermediate, un-released versions have a twelve-digit hexadecimal code attached, just like in the Development Branch.