From b50dd34887e8ae790e18cde55f923f7143d04bae Mon Sep 17 00:00:00 2001 From: Devon Hudson Date: Tue, 16 Apr 2024 19:48:30 -0600 Subject: [PATCH 1/2] Clarify what part of message retention is still experimental --- docs/message_retention_policies.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md index 2746a106b3d..c64d1539b05 100644 --- a/docs/message_retention_policies.md +++ b/docs/message_retention_policies.md @@ -7,8 +7,10 @@ follow the semantics described in and allow server and room admins to configure how long messages should be kept in a homeserver's database before being purged from it. **Please note that, as this feature isn't part of the Matrix -specification yet, this implementation is to be considered as -experimental.** +specification yet, the use of `m.room.retention` events for per-room +retention policies is to be considered as experimental. However, the use +of a default message retention policy is considered a stable feature +in Synapse.** A message retention policy is mainly defined by its `max_lifetime` parameter, which defines how long a message can be kept around after From 9466b2f27a9aa50241152a496847fdb6e7a46733 Mon Sep 17 00:00:00 2001 From: Devon Hudson Date: Tue, 16 Apr 2024 19:53:01 -0600 Subject: [PATCH 2/2] Newsfile --- changelog.d/17099.doc | 1 + 1 file changed, 1 insertion(+) create mode 100644 changelog.d/17099.doc diff --git a/changelog.d/17099.doc b/changelog.d/17099.doc new file mode 100644 index 00000000000..d8d10fa53ae --- /dev/null +++ b/changelog.d/17099.doc @@ -0,0 +1 @@ +Clarify what part of message retention is still experimental.