T7253: Improve documentation about upgrades with recommendations

Improve the documentation about upgrades and rollbacks with information about how to handle settings.

content/designs/system-updates-and-rollback.md

@@ -188,6 +188,27 @@ management is not required for final users of Apertis. For example:
   way. This can be an error prone manual process and might not be accomplished
   cleanly.
 
+In relation to system settings as defined in [preferences and persistence]( {{< ref preferences-and-persistence.md >}} )
+Debian tools use a very simple approach. On package upgrades the `dpkg`
+will perform a check taking into account
+- current version default configuration file
+- new version default configuration file
+- current configuration file
+
+Different scenarios arise depending on whether user has applied changes to the
+configuration file. If current default configuration file is the same as
+current, then the user hadn't change it, which implies that it can be safely
+upgraded (if it is required).
+
+However, if the current default configuration file is different from current
+the user had applied some changes, so it can't be upgraded silently. In this
+case `dpkg` asks the user to choose the version to use. This approach is not
+suitable for automated upgrades where there is no user interaction.
+
+To overcome some of these limitations modern systems tend to use overlays
+to have a read-only partition with default values and an upper layer with
+custom values.
+
 ### ChromeOS
 
 ChromeOS uses an A/B parallel partition approach. Instead of upgrading the system