docs: tweak rel notes for weekly releases (#34335)

Author: kay-kim

doc/user/content/manage/monitor/cloud/alerting.md

@@ -44,7 +44,7 @@ Credits | Consumption rate increase by X% | Consumption rate increase by Y% | Av
 
 ## Maintenance window
 
-Materialize has a [release and a maintenance window almost every week](/releases/) at a defined [schedule](/releases/cloud-upgrade-schedule).
+Materialize has a release and a maintenance window almost every week at a defined [schedule](/releases/schedule/#cloud-upgrade-schedule).
 
 During an upgrade, clients may experience brief connection interruptions, but the service otherwise remains fully available. Alerts may get triggered during this brief period of time. For this case, you can configure your monitoring tool to avoid unnecessary alerts as follows:
 

doc/user/content/releases/_index.md

@@ -10,10 +10,15 @@ aliases:
   - /self-managed/v25.1/release-notes/
 ---
 
-## Self-Managed v26.1.0
-*Released: 2025-11-26*
+{{< note >}}
+Starting with the v26.1.0 release, Materialize releases on a weekly schedule for
+both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for details.
+{{</ note >}}
+
+## v26.1.0
+*Released Self-Managed: 2025-11-26*
 
-v26.1.0 introduces `EXPLAIN ANALYZE CLUSTER`, console bugfixes, and improvements for SQLServer Support, including the ability to create a SQLServer Source via the console.
+v26.1.0 introduces `EXPLAIN ANALYZE CLUSTER`, console bugfixes, and improvements for SQL Server support, including the ability to create a SQL Server Source via the Console.
 
 ### `EXPLAIN ANALYZE CLUSTER`
 The [`EXPLAIN ANALYZE`](/sql/explain-analyze/) statement helps analyze how objects, namely indexes or materialized views, are running. We've introduced a variation of this statement, `EXPLAIN ANALYZE CLUSTER`, which presents a summary of every object running on your current cluster.
@@ -37,7 +42,11 @@ To understand worker skew, you can run `EXPLAIN ANALYZE CLUSTER CPU WITH SKEW`,
 | materialize.public.idx_top_buyers       | u85496    | 0         | 0.99                   | 00:00:00.020932 | 00:00:00.021048 | 00:00:00.042096 |
 | materialize.public.idx_sales_by_product | u85492    | 1         | 0.82                   | 00:00:00.065211 | 00:00:00.079829 | 00:00:00.159659 |
 
-#### Upgrade notes for v26.1.0
+### Improved SQL Server support
+
+Materialize v26.1.0 includes improved support for SQLServer, including the ability to create a SQLServer Source via the console.
+
+### Upgrade notes for v26.1.0
 
 {{< include-md file="shared-content/self-managed/upgrade-notes/v26.1.md" >}}
 
@@ -188,11 +197,7 @@ See also Upgrade Notes for release specific notes.
 
 See also [General notes for upgrades](/installation/#general-notes-for-upgrades).
 
-## Self-managed release versions
-
-{{< yaml-table data="self_managed/self_managed_operator_compatibility" >}}
-
 
 ## See also
 
-- [Cloud Upgrade Schedule](/releases/cloud-upgrade-schedule/)
+- [Release Schedule](/releases/schedule/)

doc/user/content/releases/cloud-upgrade-schedule.md

@@ -0,0 +1,58 @@
+---
+title: "Release Schedule"
+description: "Release schedule for Materialize Cloud and Self-Managed"
+disable_list: true
+menu:
+  main:
+    parent: "releases"
+    weight: 50
+aliases:
+  - /releases/cloud-upgrade-schedule/
+---
+
+Starting with the v26.1.0 release, Materialize releases on a weekly schedule for
+both Cloud and Self-Managed.
+
+## Cloud upgrade schedule
+
+In general, Materialize Cloud uses the following weekly schedule to upgrade all
+regions to the latest release:
+
+Region        | Day of week | Time
+--------------|-------------|-----------------------------
+aws/eu-west-1 | Wednesday   | 2100-2300 [Europe/Dublin]
+aws/us-east-1 | Thursday    | 0500-0700 [America/New_York]
+aws/us-west-2 | Thursday    | 0500-0700 [America/New_York]
+
+
+During an upgrade, clients may experience brief connection interruptions, but
+the service otherwise remains fully available. Upgrade windows were chosen to be
+outside of business hours in the most representative time zone for the region.
+
+{{< note >}}
+
+- Materialize may occasionally deploy unscheduled releases to fix urgent bugs.
+
+- Releases may skip some weeks.
+
+- Upgrade windows follow any daylight saving time or summer time rules
+for their indicated time zone.
+{{< /note >}}
+
+You can find details about upcoming and current maintenance on the [status
+page](https://status.materialize.com). You can also use the [status page API](https://status.materialize.com/api) to programmatically access this information.
+
+[America/New_York]: https://time.is/New_York
+[Europe/Dublin]: https://time.is/Dublin
+
+## Self-Managed release schedule
+
+In general, Materialize releases new Self-Managed versions on Friday.
+
+{{< note >}}
+
+- Materialize may occasionally have unscheduled releases to fix urgent bugs.
+
+- Releases may skip some weeks.
+
+{{< /note >}}

doc/user/content/releases/schedule.md

@@ -229,10 +229,11 @@ hydration is complete**. To see whether an object is still hydrating, navigate
 to the [workflow graph](#detect) for the object in the Materialize console.
 
 Hydration time is proportional to data volume and query complexity. This means
-that you should expect objects with large volumes of data and/or complex
-queries to take longer to hydrate. You should also expect hydration to be
+that you should expect objects with large volumes of data and/or complex queries
+to take longer to hydrate. For Cloud, you should also expect hydration to be
 triggered every time a cluster is restarted or sized up, including during
-[Materialize's routine maintenance window](/releases/cloud-upgrade-schedule/).
+[Materialize Cloud's routine maintenance
+window](/releases/schedule/#cloud-upgrade-schedule).
 
 ### Unhealthy cluster
 

doc/user/content/transform-data/troubleshooting.md

@@ -5,6 +5,11 @@ columns:
   - column: Release date
   - column: Notes
 rows:
+  - Materialize Operator: v26.1.0
+    orchestratord version: v26.1.0
+    environmentd version: v26.1.0
+    Release date: "2025-11-26"
+    Notes: "See [v26.1.0 release notes](/releases/#v2610)"
   - Materialize Operator: v26.0.0
     orchestratord version: v26.0.0
     environmentd version: v26.0.0