To release the Free plugin please make sure to check all the checkboxes below.
Pre-release Checklist
[ ] Create the release branch as release-v2.0.4 based on the development branch
[ ] Make sure to directly merge or use Pull Requests to merge hotfixes or features branches into the release branch
[ ] Run composer update and check if there is any relevant update. Check if you need to lock the current version for any dependency. The --no-dev argument is optional here, since the build script will make sure to run the build with that argument.
[ ] Refresh language .pot file to update new string
[ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct
[ ] Update the version number to the next stable version. Use $ vendor/bin/robo version 2.0.4
[ ] Commit the changes to the release branch
[ ] Build the zip package using $ vendor/bin/robo build. It should create a package in the ./dist dir.
[ ] Send to the team for testing
Release Checklist
[ ] Create a Pull Request and merge the release branch it into the master branch
[ ] Merge the master branch into the development branch
[ ] Create the Github release (make sure it is based on the master branch and correct tag)
SVN Repo\
[ ] Update your working copy using $ svn update
[ ] Cleanup the trunk directory.
[ ] Unzip the built package and move files to the trunk
[ ] Remove any eventual file that shouldn't be released in the package (if you find anything, make sure to create an issue to fix the build script)
[ ] Look for new files $ svn status | grep \? and add them using $ svn add <each_file_path>
[ ] Look for removed files $ svn status | grep ! and remove them $ svn rm <each_file_path>
[ ] Create the new tag $ svn cp trunk tags/2.0.4
[ ] Commit the changes $ svn ci -m 'Releasing v2.0.4'
[ ] Wait until WordPress updates the version number and make the final test updating the plugin in a staging site
To release the Free plugin please make sure to check all the checkboxes below.
Pre-release Checklist
release-v2.0.4
based on the development branchcomposer update
and check if there is any relevant update. Check if you need to lock the current version for any dependency. The--no-dev
argument is optional here, since the build script will make sure to run the build with that argument.$ vendor/bin/robo version 2.0.4
$ vendor/bin/robo build
. It should create a package in the./dist
dir.Release Checklist
master
branchmaster
branch into thedevelopment
branchmaster
branch and correct tag)SVN Repo\
$ svn update
trunk
directory.trunk
$ svn status | grep \?
and add them using$ svn add <each_file_path>
$ svn status | grep !
and remove them$ svn rm <each_file_path>
$ svn cp trunk tags/2.0.4
$ svn ci -m 'Releasing v2.0.4'