To remove this notice (in fact, all update nags), use the following in a custom plugin: How does one dismiss the 'upgrade notice' when managing upgrades with SVN?
, retrieved 22 October 2015 from Then you can update or switch your working copy just as described above.
Typically, it is a good idea not to store this folder in a publically-accessible location, but if you want to use this system of using Subversion for updating Word Press then you have no choice.
It is, however, quite easy to prevent anyone from browsing the , if you are also using Subversion to manage anything there.
Furthermore, I liked the smaller footprint of SVN 1.7.
In typical lazy developer fashion, I went with updating SVN to version 1.7 for Mac OS X.
You can read more about Subversion, Subversion commands, and the use of Subversion in Word Press development in the Using Subversion article.
As detailed in the Using Subversion article, the Word Press Subversion repository has several branches or sections.
These commands will create a directory "blog" for your blog, and then check out (Subversion command The trailing slash on the URL, and that period at the end of the command, are both important — they make sure that downloaded files from the repository end up in the current directory; leave off that dot and you'll end up creating a new installation directory (which would be called "trunk"), which is not what you want if the current directory is the intended installation directory. This folder stores important information about the state of the checked-out repository, and may contain sensitive information such as passwords.
These commands will create a directory "blog" for your blog, and then check out (Subversion command "co"), or extract from the repository (Subversion command "export"), the stable version of Word Press you have chosen.
Do not type the "$" characters -- they are just indications of the command prompt.
All examples here assume your blog is installed in a directory called "blog".
If your blog is installed in a different directory, you will need to alter the commands shown accordingly. This section of the article assumes you have decided you want to have your blog run the latest "bleeding edge" development version of Word Press, and are willing to put up with bugs.