Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the version history link in the notes column to find details on exact release date, release notes and package and MD5s.
|CMS Version||Available||Support||End of Life||Upgrade Type||Notes||Latest Release|
|1.5||Sept 2012||Migration to 2.5|| Plan to migrate to 2.5 now
Joomla 1.5 version history
|EOL at 1.5.26|
|1.6||Aug 2011||One-click to 2.5|| Upgrade to 2.5 now
Joomla 1.6 version history
|1.7||Feb 2012||One-click to 2.5|| Upgrade to 2.5 now
Joomla 1.7 version history
|2.5||December 31st, 2014||One-click to 3.x|| Recommended as-needed basis for new installs
Joomla 2.5 version history
|3.0||May 2013||One-click to 3.1|| You should use the one click upgrade to Joomla 3.1
Joomla 3.0 version history
|3.1||Dec 2013||One-click to 3.2|| You should use the one click upgrade to Joomla 3.2
Joomla 3.1 version history
|3.2||Apr 2014||One-click to 3.5|| Recommended for most new installs
Joomla 3.2 version history
|3.5||Mar 2014||-||-||December 31st, 2016||One-click to 4.0|
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.
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. Two more STS releases follow (usually compatible with the first STS release), and the release cycle is finished by the release of an LTS release which finalizes the work of the three STS releases. The four releases in one cycle will usually be numbered [major].0,[major].1 and [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].2 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.
A Joomla! installation contain external libraries which are included with Joomla! CMS version releases. These external libraries are not part of the core code. Please read the Notes section as they may contain more information, such as a external library version change released with a maintenance release.
|CMS Version||CMS Version Supported||Mootools||Mootools More||jQuery|| jQuery UI
(Core, Widget, Mouse, Position, and Sortable)
|Bootstrap||Simple Pie||PHP Mailer||PHP UTF-8||IDNA Convert|| Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)