The one problem I have with that guide is that it directs users to use the trunk version of Wordpress from SVN – this is in fact very dangerous and can cause all sorts of pain.

I would instead recommend users

$ svn co http://svn.automattic.com/wordpress/tags/2.0.7

and then when a new version comes out,

$ svn switch http://svn.automattic.com/wordpress/tags/newversion

Granted, this takes a little more time and thought than just using trunk, but it’s well worth it!

It’d be even better if the Wordpress SVN had a stable/release tag for users to use, and as such I have opened a trac ticket requesting this. (I’m not very familiar with trac, but it seemed easy enough.)