From aa5c931e722b27e923bd9733bc3efb094d1baba4 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 4 Dec 2025 11:20:38 -0500 Subject: [PATCH] Document MongoDB version support policy --- docs/internals/release-process.rst | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/docs/internals/release-process.rst b/docs/internals/release-process.rst index 09f560217..0f78e2fd7 100644 --- a/docs/internals/release-process.rst +++ b/docs/internals/release-process.rst @@ -29,6 +29,39 @@ As a concrete example, consider a moment in time between the release of Django 5.1.x, and any active LTS branches (e.g. 4.2.x, if Django MongoDB Backend supported it). They will trigger the release of 5.2.x, 5.1.y, 4.2.z. +MongoDB version support policy +============================== + +Major versions of MongoDB have an end-of-life date and are supported for three +years beyond that through the `MongoDB Extended Lifecycle Support Add-On +`_. + +The goal of the Django MongoDB Backend MongoDB version support policy is to +ensure a supported version of Django is available through each MongoDB +version's extended lifecycle. + +The last version of Django to support a given version of MongoDB corresponds to +the long-term support release of Django whose support extends approximately +three years after the MongoDB version's end-of-life date. + +For example, MongoDB 6.0 reached its end-of-life on July 31, 2025 which means +its end of extended lifecycle support is July 2028. Since Django 5.2 LTS is +supported until April 2028 (within a few months of July 2028), it's the last +version of Django to support MongoDB 6.0. + +.. csv-table:: + :header: "Django release series", "Supported MongoDB versions" + + "6.0", "7.0, 8.0" + "5.2 LTS", "6.0, 7.0, 8.0" + +.. seealso:: + + * `Django Supported Versions + `_ + * `MongoDB Software Lifecycle Schedules + `_ + .. _branch-policy: Branch policy