Release Versioning

The JTLS-GO Development Project has establish the following configuration management numbering system for JTLS-GO. Each JTLS-GO version consists of a four digit identifier, i.j.k.l, such as 6.4.1.0.

Digit	Explanation
MAJOR 1st Digit	This is the major version number. A change in the major version number indicates that the system concept of JTLS-GO has undergone a significant change. When making a significant change, users should expect a longer than normal time to assimilate and fully understand the new capabilities and system structure of JTLS-GO. A larger than normal database content changes should be expected. For example JTLS 3.0.0.0 was the version number assigned when JTLS-GO moved to the new web-based user interface.
MINOR 2nd Digit	This is the minor version number. A change in the minor version number indicates that the JTLS-GO has significant new model functionality that required new data. A change in the minor version number means users must upgrade their database, an automatic procedure delivered with JTLS-GO, and review these databases to ensure that their scenario use the new functionality as desired and needed.
MAINTENANCE 3rd Digit	This is the maintenance version number. A change in the maintenance digit indicates that JTLS-GO is being released with "bug" fixes found by our test team and other users. It is possible that a few minor functional improvements have been added to the model, but absolutely no data changes were needed. Thus, the database structure for JTLS-GO Version 6.3.1.0 is identical to the database structure for JTLS-GO Version 6.3.0.0. Although each user must individually decide whether to implement a maintenance version, it should be noted that as a "bug" fix release, it represents the latest stable released version of JTLS-GO.
PATCH 4th Digit	This is the patch version number. A change in the patch digit indicates that an unofficial release of JTLS-GO is being used. If an individual user has a specific problem just prior to an important exercise, the JTLS-GO Development Team may fix the issue and provide the fix on a quick reaction test cycle. The issues addressed in the patch release will be formalized and included in the next maintenance release. Only the user requiring the quick fix receives notification of the release availability.