Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/rust-server-upgrade-takeover.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.
Expand Down
3 changes: 3 additions & 0 deletions docs/rust-server-upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading