mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 16:14:02 +00:00
docs: Clarify how security releases are done.
This commit is contained in:
@@ -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
|
bug fix release, transparently documenting the issue using the
|
||||||
industry-standard [CVE advisory process](https://cve.mitre.org/).
|
industry-standard [CVE advisory process](https://cve.mitre.org/).
|
||||||
|
|
||||||
When new security releases are published, we simultaneously publish
|
When new security releases are published, we simultaneously publish the fixes to
|
||||||
the fixes to the `main` and stable release branches, so
|
the `main` branch and the release branch for the current major release series.
|
||||||
that anyone using those branches can immediately upgrade as well.
|
|
||||||
|
|
||||||
See also our [security overview][security-overview], and our [guide on securing
|
See also our [security overview][security-overview], and our [guide on securing
|
||||||
your Zulip server][securing-your-zulip-server].
|
your Zulip server][securing-your-zulip-server].
|
||||||
|
Reference in New Issue
Block a user