編輯“WordPress:WPMU SVN Repository”

=== WPMU Core Code ===

Wordpress MU development code is hosted at Automattic, at
http://svn.automattic.com/wordpress-mu/

The latest version can be seen at:
http://svn.automattic.com/wordpress-mu/trunk/

It's possible to see the past state of wpmu releases through wpmu's tags.
http://svn.automattic.com/wordpress-mu/tags/

Instead of installing from tgz or zip file, you can get Subversion to look after all the stock files in your installation. This means when a new release comes out you don't need to look through everything to work out what has changed. Instead you can simply ask SVN to update to the latest version.

SVN maintains both tagged versions (these roughly correspond to releases), and the HEAD version (latest bleeding edge beta). Unless you are actively developing you are advised to Run of a tagged copy. 

==== Running off the SVN head ====
DO NOT DO THIS FOR PRODUCTION INSTALLS.

You can run WPMU off the SVN head by:

* svn co http://svn.automattic.com/wordpress-mu/trunk/ .
* and then running the installation instructions

Note the [[WordPress:WPMU Development Methodology]] - there can be bugs trying to run the HEAD of the SVN checkout.

==== Running off a tagged version ====

Rather than running off the HEAD of SVN, which can include unconcluded or incomplete changes, some people favour running off a tagged version, and then, once a later version has been complete and released, switch the install to use a later tag. 

Tagged versions are selected just like a checkout of the HEAD.

* svn co http://svn.automattic.com/wordpress-mu/tags/2.6/ .

==== Updating WPMU to run off a later tag ====


* svn switch http://svn.automattic.com/wordpress-mu/tags/2.6/

This will replace all files that were associated with the tagged files from the repository (in our example, from 1.5.1) to the newer version, 2.6.

Naturally you can use the same method to go backwards, to an older version. 

http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.ref.svn.c.switch

=== WP Plugin SVN Code ===

Although the code for (some?) plugins is held in 

http://svn.wp-plugins.org/

There is no known way of keeping those plugins up to date with the latest stable releases. Note also that whereas wpmu core is under the strict watchful eye of donncha, the plugins repository is open to submission by anyone. You take your chances!


=== Vendor Branches ===

Subversion has the mechanism to help you bring in a third party codebase into your own repository. This is described here:
* http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html
and here:
* http://svn.haxx.se/users/archive-2006-08/0492.shtml

It would be useful if someone reconciled this for use with wpmu and wp-plugins and one's own code.

Some potentially useful strategies:
* [http://64.233.179.104/translate_c?u=http%3A%2F%2Fwww.jeffhung.net%2Fblog%2Farticles%2Fjeffhung%2F1028%2F&langpair=zh-CN|en&hl=en&ie=UTF8 Jeff Hung's SVK method]
* [http://protocol7.com/archives/2007/12/26/decent-wp-setup-2/ Niklas Protocol 7's method]

Ideally we could do with a strategy that takes the best of these two. Perhaps you'd like to add a how-to onto Codex?