Do I still need to include the update scripts in version 1.2 so people can update the plugin from v1.1 directly to v1.3? Yes. Is there a way for WordPress to automatically download v1.2, run the update scripts, and then download v1.3… No. …is there a way to flag v1.3 of my plugin and say, … Read more
To my knowledge it is not possible to generically clone/checkout the latest stable version with either git or svn. In either case you have to identify the specific tag (version) you want to pull from with git or svn. Or, as you’ve done, just pull trunk (which is the development branch) For more see: https://codex.wordpress.org/Using_Subversion
I have a similar workflow. I use GitHub Updater to manage all of my 1st party plugins and themes. The versioning, which is specified in the GHU documentation, is Semantic Versioning. x.x.x, 1.0.4, or whatever. There’s a philosophy behind SemVar and I follow that. I install the GitHub Updater and then install all my 1st … Read more
Well, nothing prevents from using Subversion for solving this tasks Note: some steps may differ depending on layout of your own repository for themes/plugins (I suppose, they are dirs inside trunk, and the whole tree doesn’t repeat standard WP-layout: /wp-content/themes/ wp-content/plugins/) In order to start you have to have: Empty Subversion repository, in which you … Read more
If you don’t want the designers to setup a revision control on each computer (this is the normal route), set up the designers on one cloud/remote server with SVN ( or even better a DVCS) that the dev teams can pull/push to. This technique can be combined for further control, this is done so team … Read more
If I’m working on whole project for a client (WP install + custom theme + plugins), I put everything in one repository. My thinking is that I created one “solution” based on WP + some existing plugins + my added code, and thus I should track it as one solution. When WP or a plugin … Read more
The most prudent way is to use a staging server. The workflow would be: DVCS (git, mercurial) Remote repository for multiple users (self hosted, github, bitbucket, etc,). Staging server, push master files to. If all is good send the files from staging to live. Some Notes: Have only one/two people actually manage the master push … Read more
Problem Analysis To get information about installed plugins, which provides plugin’s version, we’ll use get_plugins() function. Keep in mind, that this function is available in back end only, so our code must reside there. Data, returned from this function, does not tell us, which plugins are active. To filter out active plugins, we’ll use get_option(‘active_plugins’) … Read more
This is more a git question than a WordPress one IMHO, but what you need to do is write a bash script and associate with a git hook that does what you want.
Have you looked at VVV ? Varying Vagrant Vagrants is designed to support WordPress plugin and theme development using vagrant boxes and github version control. https://github.com/Varying-Vagrant-Vagrants/VVV Re Github/Bitbucket – you may possibly use one master and then have a branch per subdomain if there is enough commonality, but from the very vague information you have … Read more