From 8ca9369c13722749897a5382c455ee0bad2ad7aa Mon Sep 17 00:00:00 2001 From: Niels Lange Date: Tue, 15 Aug 2023 18:25:52 +0200 Subject: [PATCH] Update release-initial-checklist.md --- .github/release-initial-checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/release-initial-checklist.md b/.github/release-initial-checklist.md index 1c64ff15f77..958a8bc038e 100644 --- a/.github/release-initial-checklist.md +++ b/.github/release-initial-checklist.md @@ -81,7 +81,7 @@ Each porter is responsible for testing the PRs that fall under the focus of thei ## After Workflow completes -- [ ] Port to `trunk` the changes to the changelog, testing steps and required versions that you did in the previous steps. You can do so copy-and-pasting the changes in a new commit directly to `trunk`, or cherry-picking the commits that introduced those changes. +- [ ] Move the changes to the changelog, testing steps and required versions that you did in the previous steps to `trunk`. You can do so copy-and-pasting the changes in a new commit directly to `trunk`, or cherry-picking the commits that introduced those changes. - [ ] Run `npm run change-versions` to update the version in `trunk` to the next version of the plugin and include the `dev` suffix. For example, if you released 2.5.0, you should update the version in `trunk` to 2.6.0-dev. - [ ] Update the schedules p2 with the shipped date for the release (PdToLP-K-p2). - [ ] Edit the GitHub milestone of the release you just shipped and add the current date as the due date (this is used to track ship date as well).