What version of Joomla! should you use?
From Joomla! Documentation
First of all, you may want to check which version of Joomla! is running on your website.
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.
- Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.
- The latest version can be downloaded from Joomla! Downloads site.
- Make sure you subscribe to the Joomla! Security Announcements feed. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.
- If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and/or security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.
Joomla! CMS versions
|CMS Version||Available||Support||End of Life||Upgrade Type||Notes||Latest Release|
|3.9||3.10 release||One-click||Recommended for all new installs
Joomla! 3.9 version history
|3.8||3.9 release||One-click||Upgrade to 3.9.16 now
Joomla! 3.8 version history
|3.7||3.8 release||One-click||Upgrade to 3.9.16 now
Joomla! 3.7 version history
|3.6||3.7 release||One-click||Upgrade to 3.9.16 now
Joomla! 3.6 version history
|3.5||3.6 release||One-click||Upgrade to 3.9.16 now
Joomla 3.5 version history
|3.4||3.5 release||One-click||Upgrade to 3.9.16 now
Joomla 3.4 version history
|3.3||3.4 release||One-click||Upgrade to 3.9.16 now
Joomla 3.3 version history
|3.2||Oct 2014||One-click||Upgrade server's PHP to 5.3.10 or greater and upgrade to 3.9.16 now
Joomla 3.2 version history
|3.1||Dec 2013||One-click||Upgrade to 3.9.16 now
Joomla 3.1 version history
|3.0||May 2013||One-click||Upgrade to 3.9.16 now
Joomla 3.0 version history
|2.5||December 31st, 2014||Migration to 3.x||Upgrade to 3.9.16 now
Joomla 2.5 version history
|1.7||Feb 2012||Migration to 3.x||Plan to migrate to 3.9.16 now
Joomla 1.7 version history
|1.6||Aug 2011||Migration to 3.x||Plan to migrate to 3.9.16 now
Joomla 1.6 version history
|1.5||Sept 2012||Migration to 3.x||Plan to migrate to 3.9.16 now
Joomla 1.5 version history
|EOL at 1.5.26|
|1.0||22 July 2009||Migration to 3.x||Plan to migrate to 3.9.16 now||EOL at 1.0.15|
Included External Libraries
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.
External Libraries by Joomla 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)
|password _compat||lessphp||random _compat|
Joomla! versions explained
This page provides a summary of the current development strategy published on 25 April 2014. All Joomla versions released before 25 April 2014 have been developed according to previous release and support cycle. You should read the full text of the Joomla development strategy for a more detailed explanation.
Joomla! is developed following Semantic Versioning (2.0.0). The use of LTS (Long Term Support) and STS (Short Term Support) is no longer relevant or observed. The terms found directly below will be used for clarity. You should understand these terms and their meanings.
- supported - latest minor version(s) of a major version will receive patches which will include bug and security fixes
- current - the youngest or 'latest' major.x.x officially released version
- legacy - any major.minor.patch version(s) which are not the current version
- stable - major version ready for use in a production environment implied with current and legacy
- EOS - an acronym for 'end of support' which indicates no further patches will be released for bugs or security fixes
- EOL - an acronym for 'end of life' which indicates the same meaning as EOS
Each major version of Joomla! is supported by The Joomla! ProjectTM for a limited amount of time, begenning from the initial date of its official release. Joomla will actively develop each major version for a minimum of 2 years. This may be followed by continued development of a major version as per scheduled on a major version's roadmap. A short summary would be:
- each major version will have a minimum of 4 years of support
- you should always use or update to the latest major version's minor.patch
- each minor version update released is backwards compatible with the previous minor version of the same major version
Version Numbering Explained
The version identifiers for Joomla follow a three level numerical convention where the levels are defined by the software change significance.
These 3 levels are defined as:
- An increment in the major version identifier indicates a break in backward compatibility.
- An increment in the minor version identifier indicates the addition of new features or a significant change to existing features.
- An increment in the patch version identifier indicates that bugs have been fixed.
You are using Joomla version 3.3.6. This means your version is major version 3, minor version 3, patch version 6. If a patch is released for 3.3.6, it would increase your Joomla version to 3.3.7. If a new minor version for major version 3 is released, your new Joomla version would become 3.4.0. This page will always show the current stable supported version of Joomla, including the minor and patch, in the top right corner.
References and Notes
- See J3's roadmap for time frames of all future releases of all Joomla! 3 versions.
- Bug fixes will cease April 2014, security fixes only, see http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.
"Also, for the six months after Joomla! 3.3 is released, the Joomla! Project will be releasing Security Updates for both 3.2 AND 3.3 so any new vulnerabilities can be promptly patched with a one-click update without the need to immediately update to Joomla! 3.3, giving you time to request your hosting provider to update their PHP version."
- This library is intended to provide forward compatibility with the password_* functions which were added to PHP 5.5. See password_compat git for further information.
- This library is intended to provide forward compatibility with the random_bytes and random_int functions which were added to PHP 7.0. See random_compat git for further information.
- Includes jQuery Migrate plugin 1.2.1 for backwards compatibility
- Contains some 2.1 backward compatibility defaults
- This library was deprecated for JFeedFactory in Joomla! CMS version 3.1.0
- 5.2.26 as of 3.8.3
- 5.2.23 as of 3.7.3
- 5.2.16 as of 3.6.3
- Not applicable, this library was not included with the Joomla! CMS prior to version 3.5
- Not applicable, this library was not included with the Joomla! CMS prior to version 3.4
- Not applicable, this library was not included with the Joomla! CMS prior to version 3.2. The version of FOF included in Joomla 3.2 is compatible with Joomla 2.5 however.
- Not applicable, this library was not included with the Joomla! CMS prior to version 3.2
- Not applicable, this library was not included with the Joomla! CMS prior to version 3.1.2.
- Contains a 1.2 compatibility layer
- Not applicable, this library was not included with Joomla! CMS version 2.5.
- Note, legacy is a term used to only designate the status of a version in relation to the current version. Users and developers should pay close attention to the EOS date(s) to determine the viability of legacy version use or continued use.
- Version(s) marked with alpha, beta or rc (release candidate) should be used for testing only.
- EOS may be used interchangeably with EOL. Either term indicates the 'end of support' and nothing more. Do not confuse 'EOL' to mean the software will cease to work.
- The full explanation of supported releases can be found under the heading 4.3 Supported releases on the Joomla Development Strategy document.
- An extension or template installed on major.0.x version will work on major.7.x version. Extension or template are created by a 3rd party developer and their updates are the responsibility of each developer to publish. The installation of extension or template updates are the responsibility of the user.