Development Workflow
Let's make this plugin the de-facto standard for SMTP in WordPress
I suggest development in the open. I am committed to invest at least 3 hours per week in Post-SMTP!
To streamline this repo a few things need to be restructured:
-
[x]
masterbranch with a stable version -
[ ] add a
developbranch with the unstable code for testing
Release workflow for wp.org
-
merge
develop->master -
tag a release
-
automatic deployment to wp.org (via a deployer service; maybe https://deployer.seravo.com/ but it has some problems at the moment)
Hi,
-
already done and tagged
-
There is a dev branch that needs to be reset
My workflow is based on this guide: https://gist.github.com/kasparsd/3749872
I know these kind of "manual" workflows. I think everything you can automate you should. With the deployer I mentioned above the github tag gets automatically pushed as a new release to wp.org
I for myself will never ever install subversion to my machine ever again.
Maybe just branch master to a new develop.
The notes from your old dev branch can be copied over to issues