From 742e05ad5647a4a2b175293ee8325b6ca771bd65 Mon Sep 17 00:00:00 2001
From: Oleg S <97077423+RobotSail@users.noreply.github.com>
Date: Tue, 17 Dec 2024 14:12:51 -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 74e5bc68..3b586e7b 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 `#eval` channel on Slack
+    - The `#eval` channel on Discord
     - The `dev` mailing list
 
 ### Z-Stream
@@ -61,6 +62,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 previous Z-Stream tag as the previous release (e.g. `0.15.0` precedes `0.15.1`).
 1. Announce release via the following:
     - The `#eval` channel on Slack
+    - The `#eval` channel on Discord
     - The `dev` mailing list
 
 ## Release Notes