From 01264f0575355b98aaecc36162ba2452c62b776b Mon Sep 17 00:00:00 2001 From: Brandon W Maister Date: Mon, 31 Aug 2020 15:08:18 -0400 Subject: [PATCH] Don't create an issue for the relnotes team --- .github/ISSUE_TEMPLATE/release.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md index ec3439dc30788..5d9642259190e 100644 --- a/.github/ISSUE_TEMPLATE/release.md +++ b/.github/ISSUE_TEMPLATE/release.md @@ -63,8 +63,8 @@ production readiness. - [ ] Open a PR with this change, and land it. -- [ ] Create an issue and assign it to the @MaterializeInc/release-notes team to - review the [release notes] and, if applicable, the release announcement. All +- [ ] Comment on this issue and ping the @MaterializeInc/release-notes team to + review the [release notes][] and, if applicable, the release announcement. All members of the team should leave a comment stating that the release looks good. @@ -162,7 +162,7 @@ in the infrastructure repository. All of these tests can be run in parallel. - [ ] Add the version to the website's list of versions in [`doc/user/config.toml`]. - - [ ] Ensure that the issue for checking the release notes has been closed. + - [ ] Ensure that all members of the release-notes team have signed-off on this issue. - [ ] Ensure that the announcement blog post has been published and announced, if applicable, by pinging the product team in #release.