JOTM Releases Life Cycle
The JOTM release numbering adopt the following rules:
- JOTM 1.x releases was the old JOTM that did not support the recovery of the transactions. JOTM 2.x supports the recovery.
- The second indice corresponds to major enhancements, in term of functionalities or of significant upgrade of embedded components versions. This corresponds to what will be called a "major JOTM version".
- The third indice corresponds to maintenance releases (bugs fixing).
- A SVN branch will not be systematically created when releasing a major version, but only if necessary, in case a maintenance release should be done on an oldier version of JOTM.
There are basically 3 branches of JOTM currently used:
- JOTM 2.0.11 branch: Version used for JONAS 4, still compiled with JDK 1.4.
- JOTM 2.0.13 branch: Version compiled with JDK 1.5, with some enhancements, particullary about the transaction recevery. This version is not used by JONAS and should not be used any longer, since JOTM 2.1 is now mature enough.
- trunk (today JOTM 2.1): Current version, used in JONAS 5. This version have been mavenised, and implies a JDK 1.5 or more.
The releasing process for a major version is described below:
- Any JOTM version is always firstly released as release candidate, e.g. 2.1.2 (some versions may have been tagged, but not released). After some period (at least a couple of weeks) of beta testing by the community, if no bug is raised, the version is promoted as stable release, else, bugs are fixed and a new version is released (e.g. 2.1.3). No stable release will be issued until any bug with level > 5 is fixed (or a turn around is found).
- After a major version has been released as stable, no more version will be done in the corresponding branch, except some maintenance releases for some specific user requirement.