@@ -289,20 +289,18 @@ The following steps involve setting a **content-freeze** period on the project.
2892894 . Import content using either of the following approaches:
290290 1 . [ Restore content and media] ( ../deployment/restoring-content/ ) directly from the backoffice.
291291 2 . Use the [ Database Backup and Restore] ( ../databases/backups.md ) functionality in the Cloud Portal.
292- 5 . Follow [ Step 1] ( major-upgrades.md#step-1-enable-.net ) for the next environment in the line.
293- 6 . Deploy the upgrade from the left-most environment (Development).
294- 7 . Verify and test all functionality on the upgraded environment.
295- 8 . [ Remove your custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) from the production environment.
296- 9 . Ensure the hostname(s) no longer point to the production environment.
297- 10 . [ Add the custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) to the new environment (Staging).
298- 11 . Follow [ Step 1] ( major-upgrades.md#step-1-enable-.net ) for the production environment.
299- 12 . Deploy the upgrade to the production environment.
292+ 5 . Deploy the upgrade from the left-most environment (Development).
293+ 6 . Verify and test all functionality on the upgraded environment.
294+ 7 . [ Remove your custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) from the production environment.
295+ 8 . Ensure the hostname(s) no longer point to the production environment.
296+ 9 . [ Add the custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) to the new environment (Staging).
297+ 10 . Deploy the upgrade to the production environment.
300298 1 . In case the upgrade is taking longer than expected, restore a backup of the Staging database on the production environment.
301- 13 . Cancel ** content-freeze** .
302- 14 . Verify and test all functionality in the production environment.
303- 15 . [ Remove your custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) from the Staging environment.
304- 16 . Ensure the hostname(s) no longer point to the Staging environment.
305- 17 . [ Add the custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) to the production environment.
299+ 11 . Cancel ** content-freeze** .
300+ 12 . Verify and test all functionality in the production environment.
301+ 13 . [ Remove your custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) from the Staging environment.
302+ 14 . Ensure the hostname(s) no longer point to the Staging environment.
303+ 15 . [ Add the custom hostname(s)] ( ../set-up/project-settings/manage-hostnames/ ) to the production environment.
306304{% endtab %}
307305
308306{% tab title="Without content freeze" %}
0 commit comments