Release and support cycle
From Joomla! Documentation
Revision as of 13:00, 19 January 2013 by Terryarthur
Joomla! is developed using a fixed release cycle. Every six months, the Joomla! Project releases a new minor or major version of Joomla!. Joomla!'s version format is:
Each version of Joomla! is supported by the Joomla! Project for a limited amount of time. There are two classifications for support: short term support (STS) and long term support (LTS). Every fourth release will be assigned long term support.
- STS (short term support) releases are supported for seven months. Their support ends one month after the next release of Joomla is released.
- LTS (long term support) releases are supported for twenty-seven months.
Please note that both STS and LTS releases, once they have reached the GA (General Availability) status, are fully functional and ready to be used in production environment. The disadvantage of using STS releases is that you will need to update your installation of Joomla! every six months, while the advantage is that you will have access to new features and extensions earlier.
Generally, the first STS release after an LTS release indicates the beginning of a new major release cycle. This STS release introduces fundamentally new features and changes that break compatibility with the previous LTS. One more STS release follows (usually compatible with the first STS release), and the release cycle is finished by the release of an LTS release which finalizes of the work of the two STS releases. The four releases in one cycle will usually be numbered [major].0 and [major].1 [major].2 (STS) and [major].5 (LTS). For example, the STS release 3.0 will include breaking changes from 2.5, and 3.5 will include matured versions of the changes in 3.0, 3.1 and 3.2.
Usually, there will be a migration path (an officially supported way of migrating to the next version) between two LTS releases (from [major].5 to [next major].5) and between an LTS release and the STS releases in its major release cycle (from [major].1 to [major].5, for example), but not necessarily to the following STS releases (from [major].5 to [next major].0). In the case of 1.5 to 2.5 (LTS to LTS), for example, there is a migration path. Note that in the case of 2.5 to 3.0 (LTS to STS), there is also built-in migration path, since the changes aren't too incompatible.
For more information, see the official Development Strategy.