Finalize and publish the Release Tracks doc-site announcement

[sfreudenthaler]

Finalize and publish the Release Tracks doc-site announcement

Parent epic: #35693 · Workstream A (Launch mechanics) · Target: Jul 22

Background

A doc-site announcement/policy page for Evergreen Release Tracks exists in draft (unpublished). It is the canonical customer-facing reference support points customers at. It must describe each track, the two-week recalculation cadence, and how track changes are requested today.

Scope

• Finalize the draft release-policy page: define Latest / Standard / Trailing and their lag windows.
• Document the two-week maintenance-window recalculation cadence (align wording with Rebuild track promotion engine to honor 2-week maintenance-window cadence #36520).
• Document forward-only track moves (moving slower does not roll a version back).
• Document the interim track-change process (support ticket) until self-service ships.
• Confirm final track naming with product/marketing before publish.
• Publish the page and verify the live URL.

Out of scope

• Documenting the self-service UI or public API (Workstream B, not yet built).
• Cadence-selection or version-pinning (deferred by the epic).

Acceptance criteria

• Page defines all three tracks with their stabilization windows.
• Two-week cadence and forward-only semantics documented and consistent with Rebuild track promotion engine to honor 2-week maintenance-window cadence #36520.
• Interim support-ticket change process documented.
• Final naming confirmed; page published and reachable at a public URL.

Depends on

• Rebuild track promotion engine to honor 2-week maintenance-window cadence #36520 (cadence/windows must be settled before documenting them).

Blocks

• dotCMS/private-issues#653 (enablement shares this source of truth).

Part of the Evergreen Release Tracks epic. Parent: #35693.

[sfreudenthaler]

published
https://dev.dotcms.com/docs/evergreen-tracks