Mobilizon
/
connector-wordpress
mirror of https://github.com/dwaxweiler/connector-mobilizon
1
0
Fork 0
Code Issues Releases Wiki Activity

clarify two steps in release procedure

This commit is contained in:
Daniel Waxweiler 2024-04-06 08:27:24 +02:00
parent 46170377af
commit 82800a9db3
1 changed files with 17 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
README.md
View File

@ -22,21 +22,23 @@ 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. 1. Make sure `changelog.txt` is up-to-date.
2. Use a new version number and copy over the new section into `readme.txt`. 2. Create a new section with a new version number.
3. Update `package.json` with the same version number. 3. Copy over the new section into `readme.txt`.
4. Update the `package-lock.json`: `npm i --package-lock-only` 4. Update `package.json` with the same version number.
5. Build: `npm run build-prod` 5. Update the `package-lock.json`: `npm i --package-lock-only`
6. Make sure screenshots are up-to-date. 6. Build: `npm run build-prod`
7. Copy the built plugin into `/trunk` of SVN. 7. Make sure screenshots are up-to-date.
8. Create a new tag of the new version: `svn cp trunk tags/<version>` 8. Copy the built plugin into `/trunk` of SVN.
9. Check the version number occurrences in both folders. 9. Create a new tag of the new version: `svn cp trunk tags/<version>`
10. Commit everything together to the release SVN: `svn ci -m "release version <version>"` Make sure to add new files beforehand. 10. Check the version number occurrences in both folders.
11. Commit the new version in git with the same message. 11. Make sure to handle exclamation and question marks in `svn status`.
12. Tag the new version: `git tag v<version>` 12. Commit everything together to the release SVN: `svn ci -m "release version <version>"`
13. Push the new tag to the repository: `git push --tags` 13. Commit the new version in git with the same message.
14. Append `-next` to the version number in `package.json`. 14. Tag the new version: `git tag v<version>`
15. Update the `package-lock.json`: `npm i --package-lock-only` 15. Push the new tag to the repository: `git push --tags`
16. Commit: `git commit -am "prepare next release"` 16. Append `-next` to the version number in `package.json`.
17. Update the `package-lock.json`: `npm i --package-lock-only`
18. Commit: `git commit -am "prepare next release"`
### Other commands ### Other commands