Keep the release candidate off the live site
WordPress labels 7.2 RC1 as software for testing. Do not install it on a production or mission-critical site. A release candidate can still contain defects or changes that affect a plugin or theme.
Create a staging copy with access controls. Remove or replace real customer data. Disable outbound email and payment actions so that a test does not contact customers or create live transactions.
Test the parts your site depends on
Check the editor, navigation, forms, search, media uploads, checkout and account flows. Test keyboard use and mobile layouts. Review each plugin and theme that handles user input, payment or personal data.
Read the plugin developer’s compatibility guidance. Report reproducible defects through the project’s release process. Do not assume that a successful dashboard load means all important features work.
Plan the final upgrade
Track the planned final release date and wait for the stable release before upgrading production. Take a backup and confirm the restore steps before the change.
After the stable release, apply the update through a controlled process. Check the site and logs, then record the installed version and any plugin that needs follow-up.
