Aaron Brazell

Whenever you make an SVN commit on a <a href="http://code.google.com" rel="nofollow ugc">Google Code</a> project, you can instruct Google to send a notice to someplace else. Utilizing the upcoming custom post type functionality in WordPress 3.0, this plugin creates a new content type called SVN and inserts the post commit messages from Google Code into WordPress.
This plugin serves as a functional example of how custom post types are supposed to work. At the time of this release, WordPress 3.0 is not out and thus not officially supported in word or implication. Do not ask me to support custom content types. 🙂
Also, because WordPress 3.0 is pre-release, the functionality might (but probably won’t) change. I’ll do my best to keep this up to date.
Note, you must have WordPress 3.0 (pre-release) and PHP 5.2+
<h3>Arbitrary</h3>
Someone asked me what my favorite thing is? Battle unicorns. That is all… carry on.

Google Code Commit Tracking

Logs Google Code subversion post commit messages into WordPress.

Scott Cariss

Automatic upgrades on live sites are, we think most people would agree, a Bad Idea. You can’t test them before they go live; they’ll play havoc with your version control system, if you’re using one; and if they fail or screw up, your live site is broken. Bad. Idea.
Enter Staunch. Staunch makes you stick to best practice for upgrades, by preventing even admins and superadmins from running WordPress’s automatic upgrade processes on your live site.
When you want to upgrade WordPress, you can do so on a local or development install of your site; after you’ve tested it and made sure everything’s okay, you can then deploy the site as you usually would — through version control, FTP, or something else.

Staunch

A WordPress plugin to prevent automatic updates on your live sites.

Google Code Commit Tracking vs Staunch