Releases notation

From Tangra Framework Wiki

Tangra framework consist of 3 main components and they have independent versions as follows:

• Tangra Code Library - starting version will be 2.0.0dev1. Counting starts from 2 because there was 1.0.0 version which was not publicly released and we want to avoid problems with backwards compatibility on systems that already use TCL. Filename of released package will be like tangra_code_library_X.X.Xsuffix where X.X.Xsuffix reflects current version of TCL.
• Tangra Modules - Each module will have it's own version starting from 1.0.0. Initially modules will be released in "all-in-one" packages, i.e. all modules in one zip/tar.gz/tar.bz2. Filename of such package will be tangra_modules_aio_buildXXX where XXX reflects current Subversion revision.
• Tangra Control Center - starting version will be 1.0.0dev1. Filename of released package will be like tangra_control_center_X.X.Xsuffix where X.X.Xsuffix reflects current version of TCC.

Each of above components will have separate release file, i.e. zip/tar.gz/tar.bz2.

There will be so called "all-in-one" releases of Tangra Framework that will contain all of the 3 components bundled together. Bundled versions of the components will be coherent to each other, i.e. when you download "all-in-one" package you can be sure that TCC works with TCL and so on. Filenames of such release will be like tangra_framework_aio_buildYYYYMMDD where YYYYMMDD is the release data (If more than one release is published subsequent releases will have also suffix -2, -3, etc.).

Please don't confuse Tangra Modules (TM) "all-in-one" packages and Tangra Framework "all-in-one" packages. First will contain just modules, second will contain TCL, TM and TCC.

Version notations:

Let's take for example TCL ver 2.0.0dev1.

First digit shows major version (it example = 2). It will be incremented when big changes are introduced that break backward compatibility.

Second digit shows minor version (0). It will increment when new functionality/code is added .

Third digit is so called "release". It will increment when bugfixes are applyed.

Changing First digit resets to 0 second and third. Changing second digit resets to 0 third.

First, second and third digits are mandatory and always present.

There is optional suffix that may start with: RC, beta, alpha or dev (in the example = dev1). Suffix may end with digit(s).

Suffix shows maturity of the release:

• Lack of suffix - official stable release.
• RC - Release candidate. Such releases are believed to be stable by Tangra core developers and are provided in order more people to have a chance to test it. RCs are not recomended for production environments.
• beta - such releases represent "complete product" but contain known defects/bugs and are released in order remaining functionality to be tested (which is believed to be OK).
• alpha - "product" is in incomplete state, i.e. planned functionality is missing but is released in order existing functionality to be tested.
• dev - development release. Such releases will be used just for the first few months before getting into alpha state. Purpose is Tangra framework to be exposed to larger audience and feedback to be gathered about bugs, feature request, existing bad design/architecture decisions (if any) and so on.