Release Process

Merging branches

All work committed should be on a new branch, submitted in a pull request to be merged into the master branch. If there is a bug fix to be released ahead of the pending items in the master branch, then tag the patch branch, use it for the deployment, and then merge it into the master branch.

For help with Git and GitHub, please go to Working-with-Git-and-GitHub.

Bump version and changelog

The following files are updated with changelog information and version numbers:

• readme.txt
• weforms.php
• package.json

Run the build process

[ferris@bueller weforms](master)$ grunt release

[ferris@bueller weforms](master)$ git commit -am 'Build for release'

Testing Release

Once all branches are merged and release zips are created via grunt, test to make sure major functionality of the plugin is working such as submitting, editing, and creating forms. These tests should be done with script debug set to false. This will ensure that all files were concatenated and minified correctly and are working.

Tag the release

Create a new tag of the master (or other) branch using the new version number, and push it up to GitHub.

Publish in the WordPress.org directory

In order to publish to the WordPress SVN repository, you must have valid credentials to authenticate and write to the repository.

The committers are listed in the Plugin Advanced page.

If you do not have a local copy of the SVN repo, then checkout the remote copy using the following commands:

mkdir -p ~/svn/wp-plugins/weforms
cd ~/svn/wp-plugins/
svn checkout https://plugins.svn.wordpress.org/weforms

1. In SSH, change to your Git repo directory and run the plugin-deploy.sh bash script with an optional SVN comment.

[ferris@bueller weforms](master)$ ./plugin-deploy.sh "Patch release"

Documentation

1. Update the GitHub release tag to have a description containing the changelog items.
2. Broadcast an announcement for the release in The IMH Slack #boldgrid-release channel.