From a4e29350a84ed3185fd10e8cda0db849fd189580 Mon Sep 17 00:00:00 2001
From: Oleg S <97077423+RobotSail@users.noreply.github.com>
Date: Tue, 17 Dec 2024 14:03:54 -0500
Subject: [PATCH] feat: update release-strategy to include discord

In order to facilliate the addition of Discord as a new chat platform, we will be mirroring
all announcements made regarding releases as currently happens on Slack to also take place
on Discord. This commit updates our policy document to reflect this change

Signed-off-by: Oleg S <97077423+RobotSail@users.noreply.github.com>
---
 docs/release-strategy.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/release-strategy.md b/docs/release-strategy.md
index 668d2fc3..b201ffb6 100644
--- a/docs/release-strategy.md
+++ b/docs/release-strategy.md
@@ -52,6 +52,7 @@ The following are the steps for how Y-stream and Z-stream releases gets cut.
 1. Create a new release on GitHub targeting the release branch and using the latest Y-Stream tag as the previous release (e.g. `0.15.1` precedes `0.16.0`).
 1. Announce release via the following:
     - The `#sdg` channel on Slack
+    - The `#sdg` channel on Discord
     - The `dev` mailing list
 
 ### Z-Stream
@@ -61,4 +62,5 @@ The following are the steps for how Y-stream and Z-stream releases gets cut.
 1. Create a new release on GitHub targeting the release branch and using the previous Z-Stream tag as the previous release (e.g. `0.15.0` precedes `0.15.1`).
 1. If changes warrant an announcement, announce via the following:
     - The `#sdg` channel on Slack
+    - The `#sdg` channel on Discord
     - The `dev` mailing list