From b256b0206faf6035c6b9f046b9a68c036dafb45e Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Fri, 25 Oct 2024 11:06:40 +0200 Subject: [PATCH 1/3] Update README.md Added a comment on patch upgrades. --- umbraco-cloud/product-upgrades/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/umbraco-cloud/product-upgrades/README.md b/umbraco-cloud/product-upgrades/README.md index b832649999c..52bbf1b910a 100644 --- a/umbraco-cloud/product-upgrades/README.md +++ b/umbraco-cloud/product-upgrades/README.md @@ -57,6 +57,8 @@ This describes how a Umbraco Cloud project is auto-upgraded: * The failed upgrade is then tracked for reporting and the customer will be notified if necessary * When the Dev site is upgraded successfully, the upgrader will continue this same process for the next environment in the chain (that is Dev -> Staging -> Live) depending on the number of environments that exist for the project. +{% hint style="info" %} Please note that changes for patches might appear on Development, even if the same changes have been added to Live already. This is due to the environments not being synchronized during the upgrade process, as this risks pushing something from one environment to another which is not intended. Those changes just needs to be deployed and the environments are in sync again. {% endhint %} + ## How do baseline updates work? The upgrade process for patch and minor versions is the same for projects with child projects created off them. The difference is that we always upgrade the baseline as the first project, and afterward we upgrade the child projects. This ensures that any updates done from the baseline will also send the upgrade to the children. From 774cb477f617d3b7b9003053e65ffa5cc24af508 Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Fri, 25 Oct 2024 12:14:17 +0200 Subject: [PATCH 2/3] Update README.md --- umbraco-cloud/product-upgrades/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/product-upgrades/README.md b/umbraco-cloud/product-upgrades/README.md index 52bbf1b910a..22acfbd979b 100644 --- a/umbraco-cloud/product-upgrades/README.md +++ b/umbraco-cloud/product-upgrades/README.md @@ -57,7 +57,7 @@ This describes how a Umbraco Cloud project is auto-upgraded: * The failed upgrade is then tracked for reporting and the customer will be notified if necessary * When the Dev site is upgraded successfully, the upgrader will continue this same process for the next environment in the chain (that is Dev -> Staging -> Live) depending on the number of environments that exist for the project. -{% hint style="info" %} Please note that changes for patches might appear on Development, even if the same changes have been added to Live already. This is due to the environments not being synchronized during the upgrade process, as this risks pushing something from one environment to another which is not intended. Those changes just needs to be deployed and the environments are in sync again. {% endhint %} +{% hint style="info" %} Note that changes for patches might appear on Development, even if they have already been applied to Live. The environments will not be synchronized during the upgrade process. This is because synchronization risks pushing other apparent changes from one environment to another. Those changes will need to be deployed. Once that has been done, the environments will be in sync again. {% endhint %} ## How do baseline updates work? From bec534e1e847725f8485126d2ab46e0a61ca1f64 Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Fri, 25 Oct 2024 12:17:18 +0200 Subject: [PATCH 3/3] Update README.md --- umbraco-cloud/product-upgrades/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/product-upgrades/README.md b/umbraco-cloud/product-upgrades/README.md index 22acfbd979b..5fe484cb97f 100644 --- a/umbraco-cloud/product-upgrades/README.md +++ b/umbraco-cloud/product-upgrades/README.md @@ -57,7 +57,7 @@ This describes how a Umbraco Cloud project is auto-upgraded: * The failed upgrade is then tracked for reporting and the customer will be notified if necessary * When the Dev site is upgraded successfully, the upgrader will continue this same process for the next environment in the chain (that is Dev -> Staging -> Live) depending on the number of environments that exist for the project. -{% hint style="info" %} Note that changes for patches might appear on Development, even if they have already been applied to Live. The environments will not be synchronized during the upgrade process. This is because synchronization risks pushing other apparent changes from one environment to another. Those changes will need to be deployed. Once that has been done, the environments will be in sync again. {% endhint %} +{% hint style="info" %} Changes for patches might appear on Development, even if they have already been applied to Live. The environments will not be synchronized during the upgrade process. This is because synchronization risks pushing other apparent changes from one environment to another. Those changes will need to be deployed. Once that has been done, the environments will be in sync again. {% endhint %} ## How do baseline updates work?