Skip to content

feat: update release-strategy to include discord #199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 1 commit into from
Dec 17, 2024
Merged

feat: update release-strategy to include discord #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/release-strategy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down