About VortexGE Versioning

The VortexGE compressed tarball (tar.bz2) will have form  :
VortexGE-<Major Version>.<Minor Version>.<Revision Number>-<Package Number>.tar.bz2
for example :
VortexGE-0.4.3-9.tar.bz2
has :
Major Version : 0
Minor Version : 4
Revision Number : 3
Package Number 9

The "Package Number" is incremented whenever the compressed tarball is rebuilt after :
  1. Add something which are not included in the main part of VortexGE (will not change the library and the existing test application at all). An example of these changes is : adding more utility or benchmarking applications.
  2. Make minor changes to any of the source codes, documentations, or media files, or any other things. Those changes will not change the APIs and the working process of the library nor the existing test application. Examples of these changes are : changing miss-spelling words/sentences, adding pictures, sounds, beautifiers, etc.
The "Package Number" will reset to one if the "Revision Number" is incremented. Normally, releases which differ only in the "Package Number" are completely compatible.

The "Revision Number" is incremented whenever the compressed tarball is rebuilt after :
  1. Fix some bugs that may (usually not) change the APIs and the working process of the library and/or the existing test application.
  2. Make some minor modifications that may change the APIs and the working process of the library and/or the existing test application a little.
  3. Make some minor additions that should not change the APIs and the working process of the library and/or the existing test application.
Examples of these changes are : adding member functions to the existing class, change the name of any class or class' member, change any makefile, improving the source codes, etc. The "Revision Number" will reset to zero if the "Minor Version" is incremented. Normally, releases which differ in the "Revision Number" are almost completely compatible.

The "Minor Version" is incremented whenever the compressed tarball is rebuilt after :
  1. Make some modifications that may change the APIs and the working process of the library and/or the existing test application.
  2. Make some additions that should not change the APIs and the working process of the library and/or the existing test application.
Examples of these changes are : adding some classes, create more test application, etc. The "Minor Version" will reset to zero if the "Major Version" is incremented. Normally, releases which differ in the "Minor Number" are almost compatible.

The "Major Version" is incremented whenever the compressed tarball is rebuilt after :
  1. Make some major modifications and/or additions that change the APIs and the working process of the library and/or the test application. An example of these changes is : change the behavior of any existing environment.
  2. VortexGE has reach the next stage of development, for example : a new environment is added (for now there are three environments, the video environment, the 3D environment, and the audio environment).
  3. The purpose(s) of VortexGE has (have) changed.
  Normally, releases which differ in the "Major Number" still can be compatible, eventough some (medium) modifications in your codes may be needed.

Main Index