From 41ff5b5f2d7c67599c2f0f6389506f76b1bcc0af Mon Sep 17 00:00:00 2001 From: "M.P. Korstanje" Date: Fri, 9 Aug 2024 17:00:43 +0200 Subject: [PATCH] Replace even more Slack with Discord (#50) See: - https://github.com/cucumber/common/issues/2195 - https://github.com/orgs/cucumber/discussions/2197 --- RELEASING.md | 20 +++++++++----------- SUPPORT.md | 2 +- 2 files changed, 10 insertions(+), 12 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index f7cedcf..c562f7f 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -38,17 +38,15 @@ Only people with permission to push to `release/*` branches can make releases. T * Look at `CHANGELOG.md` to see what has changed since the last relesase * Use [semver](https://semver.org/) to decide on a version for the next release * If you are bumping the `MAJOR` version of `cucumber-{jvm,js,ruby}`, see the [Major release](#major-release) section -1. From the root of the polyglot project you are trying to release run: - -``` -polyglot-release -``` -1. Wait until the `release-*` workflows in GitHub Actions have passed -1. Rerun individual workflows if they fail -1. Announce the release - * in the `#newsletter` Slack channel - * on the `@cucumberbdd` Twitter account - * write a blog post +2. From the root of the polyglot project you are trying to release run: + + ``` + polyglot-release + ``` +3. Wait until the `release-*` workflows in GitHub Actions have passed +4. Rerun individual workflows if they fail +5. Announce the release + * in the `#commiters` Discord channel ### Major release diff --git a/SUPPORT.md b/SUPPORT.md index df685f3..561eda8 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -1 +1 @@ -The best way to get support if you're stuck with Cucumber is to head over to our [community Slack](https://cucumber.io/community#slack). +The best way to get support if you're stuck with Cucumber is to head over to our [community Discord](https://cucumber.io/community#discord).