Pre-Release Testing

From Joomla! Documentation

Other languages:
English • ‎français • ‎Nederlands • ‎Türkçe

Minor updates of Joomla are released every six (6) Tuesdays. One week prior to the release, the update is set for RC (Release Candidate) and available for testing. People are needed to conduct such tests. The more people that test, the better releases can be.

2021-2022 Release Dates

  • 14 September 2021
  • 26 October 2021
  • 25 May 2021
  • 7 December 2021
  • 18 January 2022
  • 1 March 2022
  • 12 April 2022
  • 24 May 2022
  • 5 July 2022
  • 16 August 2022
  • 27 September 2022
  • 8 November 2022
  • 20 December 2022

Tip: add a recurring calendar event one week before each of these dates and help the Joomla! Project test releases before they go out.

How to Test RCs

Set up a Development Location

  1. Take a backup of the site you want to test making sure you have permission to test using the website you're going to use. You can use a suggested tool (see bottom of page) or you can do this manually.
  2. Make sure your environment meets the technical requirements before proceeding.# Create a new database and new user to restore your development site to.
  3. Create a testing site or build area to work in and restore the back up copy of your site in one of the following places:

Installing the RC

  1. With your dev site established, go to Components -> Joomla! Update and then click the Options button in the top toolbar.
  2. In the field Update Channel, select Testing. In the Minimal Stability field, select Stable. Pre-Release Testing-Options en.jpg
  3. Click Save & Close in the top toolbar.
  4. Run the update on the next page.

Test, Test, Test

Test all the things you normally do on your website. Check the backend and frontend. To assist, you can also test items on the release checklist. Each release will have a new tab in the spreadsheet. Simply add your name starting in column D and report pass/fail in the cell associated with each item to test. The CMS Release Team is working on a component to make this easier. We will update this documentation when it becomes available. There may be specific items the CMS Release Team. Those items will be found on social media platforms including the Joomla! Forum. If issues are found or you need to discuss an issue, please report them on You will need a Github account to do so. Please see Filing bugs and issues for more information on how to report issues/bugs.

IMPORTANT: If you need to discuss a security issue, do NOT post on Rather send an email with details to

If you find an issue with a third-party extension, please report it directly to the developer. Do not report it to the Joomla! Project.

Finishing Up

Once done testing, remove the dev instance from your server (or local) environment. You will not be able to use it on the next release testing so killing it is best. But if you want to leave it where it is, put an .htacccess password protection over it to make sure it doesn't get indexed. Your hosting provider should be able to provide instructions on how to do this.

Suggested Tools