From 164b66f1461b3a1975f9acc4b0e3f868d7c22b1a Mon Sep 17 00:00:00 2001
From: Guy Sartorelli <36352093+GuySartorelli@users.noreply.github.com>
Date: Thu, 29 Feb 2024 14:38:56 +1300
Subject: [PATCH] DOC Refer to release policies to avoid stale information
 (#462)

---
 en/05_Contributing/09_Release_Process.md | 21 +++------------------
 1 file changed, 3 insertions(+), 18 deletions(-)

diff --git a/en/05_Contributing/09_Release_Process.md b/en/05_Contributing/09_Release_Process.md
index 0db11f0c2..03c7f90b9 100644
--- a/en/05_Contributing/09_Release_Process.md
+++ b/en/05_Contributing/09_Release_Process.md
@@ -127,24 +127,9 @@ commitment for any new APIs introduced in that minor release.
 
 ## Supported versions {#supported-versions}
 
-At any point in time, the core development team will support a set of releases to varying levels:
-
-- The status of major releases is determined by the [roadmap](http://silverstripe.org/roadmap)
-- Minor releases of major releases in "active development" or in the "bug and security fixes" phase are released roughly every three months, and their End-of-Life (EOL) is announced at least six months in advance
-- The latest minor release is supported as long as the underlying major release
-- API changes and major new features are applied to the master branch, to be included in the next major release
-- New APIs can be applied to the current minor release of major releases in "active development", but should usually be marked as "internal" APIs until they're considered stable
-- Enhancements are applied to the next minor release of major releases in "active development"
-- Non-critical bugfixes and all security fixes are applied to all supported minor releases of major releases in "active development" or in the "bug and security fixes" phase
-- Critical bugfixes and [critical security fixes](#severity-rating) are applied to the all minor releases of major releases in "active development", "bug and security fixes" or "security fixes only"
-- [Non-critical security fixes](#severity-rating) are backported to releases in the "security fixes only" phase on a best effort basis
-- Any patches applied to older minor releases are merged up regularly to newer minor releases (in the same major release)
-- Any patches applied to older major releases are merged up regularly to newer major releases
-
-Note that this only applies to the "core" recipe (the modules included by [silverstripe/recipe-core](https://github.com/silverstripe/recipe-core)
-and [silverstripe/recipe-cms](https://github.com/silverstripe/recipe-cms)).
-For [supported modules](https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/) outside of this recipe,
-please refer to our [supported modules definition](https://www.silverstripe.org/software/addons/supported-modules-definition/).
+At any point in time, the core development team will support a set of releases to varying levels. The current support status is outlined on the [roadmap](https://silverstripe.org/roadmap).
+
+See the [minor release policy](/project_governance/minor_release_policy/) and [major release policy](/project_governance/major_release_policy/) for more information.
 
 ## Deprecation