split up release procedure step to be clearer

This commit is contained in:
Daniel Waxweiler 2022-06-19 09:19:58 +02:00
parent a6f0bd9584
commit 995f6681e6
1 changed files with 13 additions and 12 deletions

View File

@ -21,18 +21,19 @@ The current changelog can be found under [source/changelog.txt](source/changelog
### Release procedure ### 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`. 1. Make sure `changelog.txt` is up-to-date.
2. Update `package.json` with the same version number. 2. Use a new version number and copy over the new section into `readme.txt`.
3. Update the `package-lock.json`: `npm i --package-lock-only` 3. Update `package.json` with the same version number.
4. Build: `npm run build-prod` 4. Update the `package-lock.json`: `npm i --package-lock-only`
5. Make sure screenshots are up-to-date. 5. Build: `npm run build-prod`
6. Copy the built plugin into `/trunk` of SVN. 6. Make sure screenshots are up-to-date.
7. Create a new tag of the new version: `svn cp trunk tags/<version>` 7. Copy the built plugin into `/trunk` of SVN.
8. Check the version number occurrences in both folders. 8. Create a new tag of the new version: `svn cp trunk tags/<version>`
9. Commit everything together to the release SVN: `svn ci -m "release version <version>"` 9. Check the version number occurrences in both folders.
10. Commit the new version in git with the same message. 10. Commit everything together to the release SVN: `svn ci -m "release version <version>"`
11. Tag the new version: `git tag v<version>` 11. Commit the new version in git with the same message.
12. Push the new tag to the repository: `git push --tags` 12. Tag the new version: `git tag v<version>`
13. Push the new tag to the repository: `git push --tags`
### Other commands ### Other commands