From 995f6681e63465d3535025d76a64dad38d679480 Mon Sep 17 00:00:00 2001 From: Daniel Waxweiler Date: Sun, 19 Jun 2022 09:19:58 +0200 Subject: [PATCH] split up release procedure step to be clearer --- README.md | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 4e80de0..0fd1b6b 100644 --- a/README.md +++ b/README.md @@ -21,18 +21,19 @@ The current changelog can be found under [source/changelog.txt](source/changelog ### Release procedure -1. Make sure `changelog.txt` is up-to-date. Use a new version number and copy over the new section into `readme.txt`. -2. Update `package.json` with the same version number. -3. Update the `package-lock.json`: `npm i --package-lock-only` -4. Build: `npm run build-prod` -5. Make sure screenshots are up-to-date. -6. Copy the built plugin into `/trunk` of SVN. -7. Create a new tag of the new version: `svn cp trunk tags/` -8. Check the version number occurrences in both folders. -9. Commit everything together to the release SVN: `svn ci -m "release version "` -10. Commit the new version in git with the same message. -11. Tag the new version: `git tag v` -12. Push the new tag to the repository: `git push --tags` +1. Make sure `changelog.txt` is up-to-date. +2. Use a new version number and copy over the new section into `readme.txt`. +3. Update `package.json` with the same version number. +4. Update the `package-lock.json`: `npm i --package-lock-only` +5. Build: `npm run build-prod` +6. Make sure screenshots are up-to-date. +7. Copy the built plugin into `/trunk` of SVN. +8. Create a new tag of the new version: `svn cp trunk tags/` +9. Check the version number occurrences in both folders. +10. Commit everything together to the release SVN: `svn ci -m "release version "` +11. Commit the new version in git with the same message. +12. Tag the new version: `git tag v` +13. Push the new tag to the repository: `git push --tags` ### Other commands