requirements.md - Add Q/A about updating tzdata

docs/general/requirements.md

@@ -300,6 +300,20 @@ If this doesn't perform a proper conversion, then you probably need to load the
 * Some managed hosts require their own process. For example, "Azure Database" has a special procedure ([`az_load_timezone()`](https://docs.microsoft.com/en-us/azure/mysql/howto-server-parameters#working-with-the-time-zone-parameter)).
   For managed hosts, you may need to consult their documentation or inquire with support.
 
+??? info "Global organizations and service-providers should consider automation."
+
+    Timezone definitions change, albeit infrequently.  For example, in 1996, Mexico adopted Daylight Savings Time (for most of its timezones); then,
+    in 2022, they dropped DST.  For computer-based clocks supporting users in Mexico, those changes require an update to the timezone data.  But it's
+    rare -- for Mexico, that represents two major changes (circa 1996 and 2022) over the span of 26 years.
+
+    The significance of timezone change is circumstantial. Compare:
+
+    * A local organization may go 20 years without needing an update. When there is a local or national change, it will be covered in the local news.
+      You may get by with infrequent/ad-hoc updates.
+    * Globally, in any given year, there will be several locales which do change their rules, and you may not be specifically aware of every change.
+      A global organization or service-provider should consider automatic updates.  For example, you might define a system-startup script or a
+      monthly cron-job to run `mysql_tzinfo_to_sql`.
+
 ### MySQL Permissions
 
 The permissions you'll need to assign to the MySQL user that CiviCRM uses will **depend on your version of MySQL**. The following example assumes you have a database called `civicrm` and a MySQL user called `civicrm_user`.