From bcdd9dc0ab10951bcbf985194fc8b7c8f35ea0d4 Mon Sep 17 00:00:00 2001 From: Richard McDaniel <1130888+rmcdaniel@users.noreply.github.com> Date: Sun, 1 Nov 2026 18:02:01 -0600 Subject: [PATCH 1/2] Rust #325: note takeover's planned deprecation in 3.1.x Takeover of PHP Server databases (layouts 2.5.14 through 2.11.8) ships in 3.0.0 for self-hosted upgrades, gets no further investment, and is planned for deprecation in the 3.1.x line (operator decision, November 1). The takeover note says so up front and the upgrade guide links to it. Co-Authored-By: Claude Opus 5.5 --- docs/rust-server-upgrade-takeover.md | 11 +++++++++++ docs/rust-server-upgrade.md | 3 +++ 2 files changed, 14 insertions(+) diff --git a/docs/rust-server-upgrade-takeover.md b/docs/rust-server-upgrade-takeover.md index 3707a32d8..4f979faf4 100644 --- a/docs/rust-server-upgrade-takeover.md +++ b/docs/rust-server-upgrade-takeover.md @@ -10,6 +10,17 @@ read, and their `backup_verified`, `php_quiescence_verified`, `stored_representation_compatibility_verified` and `takeover_allowed` flags are always false. This note says what makes each one true. +## Deprecation + +Takeover ships in 3.0.0 so self-hosted installations can upgrade a PHP Server +database (layouts 2.5.14 through 2.11.8) in place. It gets no further +investment beyond what 3.0.0 ships and is planned for deprecation in the 3.1.x +line (operator decision, November 1, 2026, recorded on +[#325](https://github.com/durable-workflow/server/issues/325)). Upgrade from +PHP while running 3.0.x; the release that deprecates takeover will say so in +its release notes. New installations, including Durable Workflow Cloud cells, +start on a fresh native database and never take over a PHP one. + ## Shape Takeover is an explicit command, never a side effect of starting the server. diff --git a/docs/rust-server-upgrade.md b/docs/rust-server-upgrade.md index 421908fc4..163fd9da7 100644 --- a/docs/rust-server-upgrade.md +++ b/docs/rust-server-upgrade.md @@ -5,6 +5,9 @@ backup-first, sequential upgrade of an existing PHP database. This document describes the first executable preparation step; production takeover remains unimplemented and unqualified. +Takeover of a PHP database is planned for deprecation in the 3.1.x line; see +[the takeover note](rust-server-upgrade-takeover.md#deprecation). + ## Read-only source inspection contract The native `upgrade-inspect` command inspects a configured existing PHP From 7b95718a60879358e653662c12b0c752492716d4 Mon Sep 17 00:00:00 2001 From: Richard McDaniel <1130888+rmcdaniel@users.noreply.github.com> Date: Sun, 1 Nov 2026 18:41:18 -0600 Subject: [PATCH 2/2] Keep the takeover deprecation's new-install guidance general General's review of #930: the self-hosted guide does not need Cloud cell terminology. Co-Authored-By: Claude Opus 5.5 --- docs/rust-server-upgrade-takeover.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/rust-server-upgrade-takeover.md b/docs/rust-server-upgrade-takeover.md index 4f979faf4..0533635dd 100644 --- a/docs/rust-server-upgrade-takeover.md +++ b/docs/rust-server-upgrade-takeover.md @@ -18,8 +18,8 @@ investment beyond what 3.0.0 ships and is planned for deprecation in the 3.1.x line (operator decision, November 1, 2026, recorded on [#325](https://github.com/durable-workflow/server/issues/325)). Upgrade from PHP while running 3.0.x; the release that deprecates takeover will say so in -its release notes. New installations, including Durable Workflow Cloud cells, -start on a fresh native database and never take over a PHP one. +its release notes. New installations start on a fresh native database and +never take over a PHP one. ## Shape