編輯“WordPress:WPMU SVN Repository”

=== WPMU 核心代碼 ===
Wordpress MU開發(fā)代碼托管在Automattic，在http://svn.automattic.com/wordpress-mu/

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

可以通過wpmu的標簽查看wpmu發(fā)行的文章狀態(tài)。
http://svn.automattic.com/wordpress-mu/tags/

不是從tgz或者壓縮文件中安裝，你可以使得子版本查看你的安裝版本中的所有儲存文件。這意味著，出現(xiàn)新的版本的時候，你不需要查找所有內(nèi)容，查看已更改了什么。你只要要求SVN更新到最新的版本即可。
 
SVN維持了tagged版本（基本上與發(fā)行版本相應），和HEAD版本（最新的bleeding edge beta）。除非你正在積極地發(fā)展，否則建議你運行tagged版本。
==== Running off the SVN head ====

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

DO NOT DO THIS FOR PRODUCTION INSTALLS.

不要為安裝的產(chǎn)品運行這個。

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發(fā)展方法]] –有一些程序缺陷試圖運行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已標記的版本，然后，一旦稍后的版本完成并且發(fā)行了，切換當前版本，使用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!

暫時還沒有什么方式可以使得這些插件與最新發(fā)行的穩(wěn)定文本同步。注意盡管donncha密切監(jiān)視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？