From 45fcf7532ca507532b8b89ef19ca65475e4dbb0f Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 6 Sep 2022 18:02:25 +0000 Subject: deploy: c9b7e9735508bb148c6ad59c433d71e5b8b360ad --- develop/deprecation_policy.html | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'develop/deprecation_policy.html') diff --git a/develop/deprecation_policy.html b/develop/deprecation_policy.html index 8c94bf8057..3cae1c2ce2 100644 --- a/develop/deprecation_policy.html +++ b/develop/deprecation_policy.html @@ -157,6 +157,10 @@ version in future releases.

Details on the upstream support life cycles for Python and PostgreSQL are documented at https://endoflife.date/python and https://endoflife.date/postgresql.

+

A Rust compiler is required to build Synapse from source. For any given release +the minimum required version may be bumped up to a recent Rust version, and so +people building from source should ensure they can fetch recent versions of Rust +(e.g. by using rustup).

Context

It is important for system admins to have a clear understanding of the platform requirements of Synapse and its deprecation policies so that they can @@ -167,6 +171,12 @@ long process.

By following the upstream support life cycles Synapse can ensure that its dependencies continue to get security patches, while not requiring system admins to constantly update their platform dependencies to the latest versions.

+

For Rust, the situation is a bit different given that a) the Rust foundation +does not generally support older Rust versions, and b) the library ecosystem +generally bump their minimum support Rust versions frequently. In general, the +Synapse team will try to avoid updating the dependency on Rust to the absolute +latest version, but introducing a formal policy is hard given the constraints of +the ecosystem.

-- cgit 1.5.1