Release and support cycle

From Joomla! Documentation

Revision as of 09:35, 24 September 2022 by Cmb (talk | contribs) (Corrected begenning to beginning. Some URL corrections.)
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Nederlands • ‎català • ‎eesti • ‎español • ‎français • ‎italiano • ‎português • ‎русский • ‎العربية • ‎فارسی • ‎中文(台灣)‎ • ‎日本語
Stable Version

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[1]
  • stable - major version ready for use in a production environment implied with current and legacy[2]
  • 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[3]

Each major version of Joomla! is supported by The Joomla! ProjectTM for a limited amount of time, beginning 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.[4] 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[5]

Please use the Joomla! CMS Development Roadmap or the Joomla! CMS versions chart to determine the estimated EOS (end of support) for each major.minor version(s) or the entire major version.

Version Numbering Explained[edit]

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:

  1. An increment in the major version identifier indicates a break in backward compatibility.
  2. An increment in the minor version identifier indicates the addition of new features or a significant change to existing features.
  3. 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.


  1. 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.
  2. Version(s) marked with alpha, beta or rc (release candidate) should be used for testing only.
  3. 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.
  4. The full explanation of supported releases can be found under the heading 4.3 Supported Releases on the Joomla Development Strategy document.
  5. 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.