More then likely it is personal preference. Some people like the workflow introduced by SVN, and some just don’t like the distributed model of Git. Some like the way commits, branches, tags etc are handled in one revision control over another. It could also be that they where using SVN before Git was stable enough … 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
The wordpress plugin repo does not have any API as far as I can tell for push and pull hooks from a 3rd party service like github. Right now the solutions are hacky at best and require you to use git as a middle man (on your computer) and also deal with SVN’s use of … Read more
You would need to have subversion installed on the same machine and command line access to the machine.
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
Dunc, glad you asked about this before it was too late for you. You have heard the right words. You are right, unfortunately the articles tutorials are not very much newbie friendly. Frist let me try to clear some terminology for you. The thing you need to manage your code and keep track of all … Read more
Externals, definitely. Set up your own SVN repo, then make WP as an external in the repo. I put it into a /wp directory. You can access the WP SVN as an external here: http://core.svn.wordpress.org/ I tend to use trunk. You can use a branch, if you really, really want. Branches get auto updated with … Read more
Simply stop running svn commands, and/or delete all the folders named “.svn” in your WordPress folder and all child folders, which removes the Subversion metadata. There is no difference between the WordPress 3.0.1 release obtained using Subversion or as a tarball from the WP downloads page, save for the .svn folders in the former. WordPress … Read more
I use Git for all my projects since it lets me work offline and that happens fairly often for me. Git can interface with SVN if you’d still like to use Git then push your plugins to WordPress.org. http://www.nkuttler.de/post/using-git-for-wordpress-development/ http://hakre.wordpress.com/2010/09/28/git-rocks/
Im going to make this answer a blog article since it went slightly off-topic GRIN. On http://wp.leau.co/2011/02/25/how-to-setup-your-wordpress-php-development-environment/ in chapter 6 I made some explanation for SVN in eclipse but you are probably looking for something else. The story I made here was about your comment “So for now I wing it with VCS integration features … Read more