From 4318bb6431b335b56b457184044ff6e2201b7884 Mon Sep 17 00:00:00 2001 From: Churikova Tetiana Date: Tue, 11 Jan 2022 15:49:27 +0100 Subject: [PATCH] github: update release umbrella issue Signed-off-by: Churikova Tetiana --- .github/ISSUE_TEMPLATE/release-issue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/release-issue.md b/.github/ISSUE_TEMPLATE/release-issue.md index 8ca75480ad..18fac5a84e 100644 --- a/.github/ISSUE_TEMPLATE/release-issue.md +++ b/.github/ISSUE_TEMPLATE/release-issue.md @@ -27,7 +27,7 @@ Upgrade (e2e): ### Process #### 1) Kick-off - [ ] 1. Translation PRs is merged before cutting branch (Jinho) -- [ ] 2. Prepare scope of visible changes based on commits history, started from previous release branch cut ([example]( https://notes.status.im/1.14-release-notes?view)) +- [ ] 2. Prepare scope of visible changes based on commits history, started from previous release branch cut ([guide](https://notes.status.im/how-to-prepare-release-notes)) - [ ] 3. Update [RELEASES.md](https://github.com/status-im/status-react/blob/develop/RELEASES.md) with release notes (make PR based on previous step) - [ ] 4. Create release branch using this [guide](https://github.com/status-im/status-react/blob/develop/doc/RELEASE_GUIDE.md), bump VERSION (merge created PR ([example](https://github.com/status-im/status-react/pull/12504) ) to develop) and get successful release builds (so, testing can be started) - [ ] 5. Based on release scope, ask for comms (Jonny)