Pre-Release Testing: Difference between revisions
From Joomla! Documentation
Changed some of the dates to reflect 4.2 releasing the day before Joomla's birthday and taking it six weeks from there. |
Some markup corrections. |
||
| Line 1: | Line 1: | ||
<noinclude><languages /></noinclude> | <noinclude><languages /></noinclude> | ||
<translate><!--T:1--> 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.</translate> | <translate><!--T:1--> 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.</translate> | ||
| Line 20: | Line 20: | ||
== <translate><!--T:5--> How to Test RCs</translate> == | == <translate><!--T:5--> How to Test RCs</translate> == | ||
=== <translate><!--T:6--> Set | === <translate><!--T:6--> Set Up a Development Location</translate> === | ||
<translate> | <translate> | ||
<!--T:7--> | <!--T:7--> | ||
| Line 26: | Line 26: | ||
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Backup Basics for a Joomla! Web Site]] | #*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Backup Basics for a Joomla! Web Site]] | ||
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|What are the best practices for site backups?]] | #*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|What are the best practices for site backups?]] | ||
# Make sure your environment meets the [http://www.joomla.org/about-joomla/technical-requirements.html technical requirements] before proceeding.</translate><translate> | # Make sure your environment meets the [http://www.joomla.org/about-joomla/technical-requirements.html technical requirements] before proceeding.</translate> | ||
<translate> | |||
<!--T:8--> | <!--T:8--> | ||
# Create a new database and new user to restore your development site to. | # Create a new database and new user to restore your development site to. | ||
# 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: | # 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: | ||
#* A subdomain. | #* A subdomain. | ||
#* A subdirectory. | #* A subdirectory. | ||
#* A local device via [https://sourceforge.net/projects/wampserver/ WAMP], [http://www.mamp.info/en/ MAMP], [http://sourceforge.net/projects/lampas/ LAMP], [https://docs.joomla.org/XAMPP XAMPP].</translate><translate> | #* A local device via [https://sourceforge.net/projects/wampserver/ WAMP], [http://www.mamp.info/en/ MAMP], [http://sourceforge.net/projects/lampas/ LAMP], [https://docs.joomla.org/XAMPP XAMPP].</translate> | ||
<translate> | |||
<!--T:9--> | <!--T:9--> | ||
#* A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration). | #* A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration). | ||
| Line 41: | Line 43: | ||
<translate> | <translate> | ||
<!--T:11--> | <!--T:11--> | ||
# With your dev site established, go to | # With your dev site established, go to {{rarr|Components,Joomla! Update}} and then click the ''Options'' button in the top toolbar. | ||
# In the field '''Update Channel''', select '''Testing'''. In the '''Minimal Stability''' field, select ''Stable''.</translate> [[File:Pre-Release Testing-Options_<translate><!--T:12--> en</translate>.jpg|border]] | # In the field '''Update Channel''', select '''Testing'''. In the '''Minimal Stability''' field, select ''Stable''.</translate> [[File:Pre-Release Testing-Options_<translate><!--T:12--> en</translate>.jpg|border]] | ||
<translate><!--T:13--> | <translate><!--T:13--> | ||
# Click '''Save & Close''' in the top toolbar. | # Click '''Save & Close''' in the top toolbar. | ||
# Run the update on the next page.</translate> | # Run the update on the next page.</translate> | ||
| Line 53: | Line 52: | ||
<translate> | <translate> | ||
<!--T:15--> | <!--T:15--> | ||
Test all the things you normally do on your website. Check the | Test all the things you normally do on your website. Check the Backend and Frontend. To assist, you can also test items on the [https://docs.google.com/spreadsheets/d/1tCgPO8_y2LT5PjsHUWBcW-5q4f8BUBODY3iuEgXWFj0/edit#gid=322644199 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.</translate> | ||
<translate> | <translate> | ||
<!--T:16--> | <!--T:16--> | ||
| Line 59: | Line 58: | ||
<translate> | <translate> | ||
<!--T:17--> | <!--T:17--> | ||
If issues are found or you need to discuss an issue, please report them on [https://issues.joomla.org/ issues.joomla.org]. You will need a Github account to do so. Please see [[S:MyLanguage/Filing bugs and issues|Filing | If issues are found or you need to discuss an issue, please report them on [https://issues.joomla.org/ issues.joomla.org]. You will need a Github account to do so. Please see [[S:MyLanguage/Filing bugs and issues|Filing Bugs and Issues]] for more information on how to make a report.</translate> | ||
<translate><!--T:18--> '''Important''' If you need to discuss a security issue, do '''not''' post on [https://issues.joomla.org/ issues.joomla.org]. Rather send an email with details to [mailto:security@joomla.org security@joomla.org].</translate> | |||
<translate><!--T:19--> 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.</translate> | <translate><!--T:19--> 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.</translate> | ||
| Line 67: | Line 66: | ||
=== <translate><!--T:20--> Finishing Up</translate> === | === <translate><!--T:20--> Finishing Up</translate> === | ||
<translate><!--T:21--> 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. | <translate><!--T:21--> 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. 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.</translate> | ||
== <translate><!--T:22--> Suggested Tools</translate> == | == <translate><!--T:22--> Suggested Tools</translate> == | ||
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] <translate><!--T:23--> for backup and restore.</translate> | * [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] <translate><!--T:23--> for backup and restore.</translate> | ||
[[Category:Bug_Squad{{#translation:}}]] | [[Category:Bug_Squad{{#translation:}}]] | ||
Revision as of 21:26, 20 September 2022
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.
2022 Release Dates
- 18 January 2022
- 15 February 2022
- 29 March 2022
- 12 April 2022
- 10 May 2022
- 21 June 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
- 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.
- Make sure your environment meets the technical requirements before proceeding.
- Create a new database and new user to restore your development site to.
- 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:
- A subdomain.
- A subdirectory.
- A local device via WAMP, MAMP, LAMP, XAMPP.
- A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration).
- Restoring a site on a local device. See Installing Joomla locally and Setting up your workstation for Joomla development.
- Restoring a site with a tool listed at bottom of page. (Read the Suggested Tools)
Installing the RC
- With your dev site established, go to Components → Joomla! Update and then click the Options button in the top toolbar.
- In the field Update Channel, select Testing. In the Minimal Stability field, select Stable.
- Click Save & Close in the top toolbar.
- 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 issues.joomla.org. You will need a Github account to do so. Please see Filing Bugs and Issues for more information on how to make a report.
Important If you need to discuss a security issue, do not post on issues.joomla.org. Rather send an email with details to security@joomla.org.
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. 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
- Akeeba Backup for backup and restore.