Install Wordpress in SVN using svn:externals
Note: This post requires working knowledge of SVN
Goals
- Keep a complete Wordpress install in your SVN
- Have the Wordpress core files checked out from their SVN
- Have as many plugins as possible checked out from their SVN
- Still provide versioning of your custom themes/plugins
Other Methods
- Copying/exporting the Wordpress files into your SVN
- Upgrading requires manually copying all the files over again
- Checkout a copy of Wordpress
- Directory will be a working copy of their SVN, any changes you make can’t be versioned in your SVN
Benefits
- Easy updates, change one line and run a command to download all the changes from a new version
- Allows you to keep your own themes or plugins in your SVN
- Easy to copy the same Wordpress install on multiple computers
- If you need to hack core Wordpress/plugin files, any new changes from new versions will be merged, or provide you with an opportunity to resolve any conflicts.
- Note that changes to these files cannot be committed to your SVN, however this should encourage you to not hack core files

A great example of a case where listening to users will not produce the most usable design. We ran into the same phenomenon when I worked on Soundtrack Pro. In many cases we wanted to reinvent how particular audio editings tasks were done, but found editors resistant to anything other than the clunky old Pro Tools ways of doing things.