Versioning

tarstall has 3 methods for version tracking, each serving a specific purpose. All 3 versions can be shown using the tarstall command without any command-line arguments.

tarstall Version: The version of tarstall as shown in x.y.z format. This currently does not follow semantic versioning conventions, and instead, the major number is incremented on insanely large changes (currently this hasn't happened) changes, the minor number incremented on major new versions, and the bugfix number incremented for extremely minor changes or bugfixes.

Ex. tarstall Version: 1.6.2

Internal Version Code: The internal version code is actually two separate version numbers being compacted into one, which is of the format file_version.program_version.

Ex. Internal Version Code 17.112

file_version: This is a version number incremented any time when a tarstall update requires changes to the file system to successfully upgrade from an old version to a newer version. For example, if tarstall's configuration file requires a new key to be added, file_version will be incremented so tarstall can make the appropriate changes at upgrade time.

program_version: Internally called prog_internal_version, this version number is incremented for every code change made to tarstall, no matter how big or small. By "code change", I mean any commit that changes the codebase to be different from what it once was in any branch. For example, a bugfix to the beta branch would increment this variable, but merging the beta branch into the master branch would NOT increment this number. tarstall uses this number to check for updates.