Release process

For each new release, these are the steps which must be followed for a successful publish of the release to the WordPress plugins repo:

1. Make any functional edits needed to the plugin code, whether in a development branch (git style) or in the master branch (svn style). If the edits are done in a development branch, they should be merged to the master branch after they are tested and approved.
2. Once the edits are ready for release, before tagging a new release, make sure the new version number is updated in bibleget-io.php
3. You may want to up the new release version number in README.md also
4. Tag the new release: this will trigger the action that will push the new tag to SVN. Best way to tag is by issuing a new release, which will also create a new branch associated with the new tag. Branch should be prefixed with v, tag should not.
5. Update the readme.txt with changelog info, upgrade notice, and stable tag. This will trigger the action that will push the readme.txt with the new stable tag, triggering the WordPress plugin repository to publish the new release. The readme.txt will be pushed both to trunk and to the tag for that release.