Rumperuu/footnotes
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Updated SVN Release Guide (markdown)

pewgeuges 2021-03-10 11:32:29 +01:00
parent 51c01e7c0c
commit 6c3909f5ec
1 changed files with 13 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
SVN-Release-Guide.md

@ -8,12 +8,17 @@ Subversion is for release control, not development. This Git repo, hosted on Git
# Pushing Code to the WP Plugin Directory # Pushing Code to the WP Plugin Directory
1. Copy the SVN repo. locally (`svn co https://plugins.svn.wordpress.org/footnotes/ footnotes-svn`) 1. Copy the SVN repo. locally (`svn co https://plugins.svn.wordpress.org/footnotes/ footnotes-svn`);
1. Enter the folder (`cd footnotes-svn`) 1. Enter the folder (`cd footnotes-svn`);
1. Copy over the files from your local copy of this repo. (**make sure you have checked out the `main` branch**) into the `trunk/` directory 1. Copy over the files from your local copy of this repo. (**make sure you have checked out the `main` branch**) into the `trunk/` directory;
1. **MAKE SURE THAT THE ‘Stable Tag’ FIELD IN `trunk/readme.txt` IS THE LATEST RELEASE VERSION, NOT DEVELOPMENT** 1. **MAKE SURE THAT THE ‘Stable Tag’ FIELD IN `trunk/readme.txt` IS THE LATEST RELEASE VERSION, NOT DEVELOPMENT!**
1. View the changes (`svn stat`) 1. View the changes (`svn stat`);
1. If you are adding/removing any files, make sure you add them to/remove them from tracking using `svn add`/`svn rm` 1. If you are adding/removing any files, make sure you add them to/remove them from tracking using `svn add`/`svn rm`
1. Commit your changes (`svn ci -m "<your message>"`) 1. Commit your changes (`svn ci -m "<your message>"`);
1. Pull down another copy of the repo. to test locally 1. Pull down another copy of the repo. to test locally;
1. When the new version is ready for release, update the ‘Stable Tag’ field in `trunk/readme.txt` and the WP Plugin Directory will automatically handle the release. 1. When the new version is ready for release, update the ‘Stable Tag’ field in `trunk/readme.txt`;
1. Make sure the version number in trunk/footnotes.php is now in sync with the Stable Tag version;
1. Copy trunk/ to its tagged folder: `svn cp trunk tags/<new version>`;
1. Commit the release: `svn ci -m $'<full changelog of that version including the heading and with line breaks converted to \n>'`
The WP Plugin Directory will automatically handle the release.