编辑“WordPress:WPMU SVN Repository”

=== WPMU 核心代码 ===
Wordpress MU开发代码托管在Automattic，在http://svn.automattic.com/wordpress-mu/

最新的版本在：
http://svn.automattic.com/wordpress-mu/trunk/

可以通过wpmu的标签查看wpmu发行的文章状态。
http://svn.automattic.com/wordpress-mu/tags/

不是从tgz或者压缩文件中安装，你可以使得子版本查看你的安装版本中的所有储存文件。这意味着，出现新的版本的时候，你不需要查找所有内容，查看已更改了什么。你只要要求SVN更新到最新的版本即可。
 
SVN维持了tagged版本（基本上与发行版本相应），和HEAD版本（最新的bleeding edge beta）。除非你正在积极地发展，否则建议你运行tagged版本。
==== Running off the SVN head ====

==== Running off the SVN head ====

DO NOT DO THIS FOR PRODUCTION INSTALLS.

不要为安装的产品运行这个。

You can run WPMU off the SVN head by:

You can run WPMU off the SVN head by:

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

* svn co http://svn.automattic.com/wordpress-mu/trunk/ .
* 然后运行安装指示

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

注意[[WordPress:WPMU Development Methodology|WPMU发展方法]] –有一些程序缺陷试图运行HEAD of the SVN checkout。

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

==== 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. 

没有running off the HEAD of SVN，这可能包含为完成的更改，一些人更喜欢running off已标记的版本，然后，一旦稍后的版本完成并且发行了，切换当前版本，使用later tag。

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

已标记版本的选择就如checkout of the HEAD。

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

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

====更新WPMU 运行稍后的标签====

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

* svn切换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.

这样将库存中的标签文件相关的文件（在我们的例子中，从1.5.1开始）替换，到更新的版本，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

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

=== WP Plugin SVN Code ===

=== WP 插件SVN 代码===

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

(一些?)插件的代码位于

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

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!

暂时还没有什么方式可以使得这些插件与最新发行的稳定文本同步。注意尽管donncha密切监视wpmu核心代码，任何人都可以向插件资源库递交插件。你碰碰运气！

=== Vendor Branches ===

=== Vendor Branches ===

Subversion has the mechanism to help you bring in a third party codebase into your own repository. This is described here:

子版本有种机制能够帮助你将第三方codebase带进你自己的库存中。在这里有描述：

* http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html
and here:
* http://svn.haxx.se/users/archive-2006-08/0492.shtml


* http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html
和这里:
* 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.

如果有人将这个与wpmu 和 wp-plugins和自己的代码用在一起，将有用。

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]




* [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?

理想地情况下，我们可以采取一种策略，完美地处理这两个方面。也许你想将how-to添加到Codex？