WordPress SVN

OK, since I’ve switched over to WordPress I have to admit it’s been pretty painless. I decided to go with the [SVN update process][1] since I know it’s much easier. But the monkey wrench in the process is having to switch to the new checkout for every stable release.
So instead of
$ cd ./blog
$ svn up
I have to do the following.
$ cd ./blog
$ svn sw http://svn.automattic.com/wordpress/tags/2.3.2/
$ svn up
Why isn’t there a symlink for the latest stable release? Then I could set up..
$ svn sw http://svn.automattic.com/wordpress/tags/current
and be done with it.
[1]: http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion

Filed under: code, computerTagged with: , ,

3 Comments

  1. I would recommend using the branch url rather than the tag:

    http://svn.automattic.com/wordpress/branches/2.3/

    That way you only have to svn switch every time there is a new major release (every 3-4 months). For all minor releases you just need to svn up (or just automate it).

  2. But Barry, is the branch current? Does it only have the 2.x releases and not the 2.x.x releases? Or does it?

  3. It’s more “current”-ish than tags. It will give you all the updates for that branch until the next branch comes out. So right now branches/2.5/ will get you v2.5.2 alpha. You can set up cron to svn up for you every night. Then, the only svn sw you have to do is at branch changes. This is the one I hit.

    If you’re feeling froggy, you can always hit trunk/. That gives you the developement version. Which works. Sometimes. But if set up cron to svn up for you every night, there’s no input from you, except for the occasional database update.

    In the end, though, I agree with you, Andy. They need a stable trunk we can point to and forget about it. I cannot think of any reason not to, and I can also think of no reason to have the current system! :-\


Comments are closed for this article!