From 36a63f7963593c221a63e9c9207cde26ba29d7da Mon Sep 17 00:00:00 2001 From: Alya Abbott Date: Fri, 17 Oct 2025 08:50:31 -0700 Subject: [PATCH] docs: Clarify how security releases are done. --- docs/overview/release-lifecycle.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/overview/release-lifecycle.md b/docs/overview/release-lifecycle.md index f37997af40..cbc29ad870 100644 --- a/docs/overview/release-lifecycle.md +++ b/docs/overview/release-lifecycle.md @@ -47,9 +47,8 @@ When we discover a security issue in Zulip, we publish a security and bug fix release, transparently documenting the issue using the industry-standard [CVE advisory process](https://cve.mitre.org/). -When new security releases are published, we simultaneously publish -the fixes to the `main` and stable release branches, so -that anyone using those branches can immediately upgrade as well. +When new security releases are published, we simultaneously publish the fixes to +the `main` branch and the release branch for the current major release series. See also our [security overview][security-overview], and our [guide on securing your Zulip server][securing-your-zulip-server].