編輯“WordPress:Reporting Bugs”（章節(jié)）

==程序錯(cuò)誤報(bào)告和解決方法概述==

There are several steps in the process of reporting and resolving a WordPress bug. Here is an overview; more details are in sections below. 

關(guān)于報(bào)告和解決WordPress程序錯(cuò)誤問題，有幾個(gè)步驟。這里是概述；更多的詳細(xì)信息，在下面的部分。

# A user finds a bug that appears to be in the core of WordPress (not in a Theme or Plugin).

#用戶在WordPress核心發(fā)現(xiàn)了一個(gè)程序錯(cuò)誤（錯(cuò)誤不是在主題或者插件中0

# The user tries to make sure it is actually a bug.  See [[WordPress:#Before You Report a Bug|Before You Report a Bug (below)]].

#用戶試著確定那的確是個(gè)程序錯(cuò)誤。請看看[[WordPress:#Before You Report a Bug|報(bào)告程序錯(cuò)誤之前 (下面的)]]。

# If it is determined to be a bug, the user submits the bug report, called a ''ticket'', to [http://trac.wordpress.org/ Trac], the WordPress bug tracking system.  See  [[WordPress:#Reporting a Bug|Reporting a Bug (below)]]. 

#如果確定那是個(gè)程序錯(cuò)誤，用戶遞交程序錯(cuò)誤報(bào)告，稱之為''ticket''，遞交到[http://trac.wordpress.org/ Trac]，WordPress程序錯(cuò)誤追蹤系統(tǒng)。請看看[[WordPress:#Reporting a Bug|報(bào)告一個(gè)程序錯(cuò)誤 (下面的)]]。

# A WordPress developer (who could be a volunteer like you) confirms that the bug does actually exist, and that it should be fixed, and marks it as such in the ticket. See [[WordPress:#Trac Keywords|Trac Keywords list (below)]] and [[WordPress:#Bug Resolutions|Bug Resolutions (below)]].

#WordPress開發(fā)人員（可能像你一樣，是個(gè)志愿者）證實(shí)了的確存在程序錯(cuò)誤，而且應(yīng)該得到解決，并且在ticket對這個(gè)錯(cuò)誤進(jìn)行標(biāo)記。請看看[[WordPress:#Trac Keywords|Trac Keywords 列表(下面的)]] 和 [[WordPress:#Bug Resolutions|程序錯(cuò)誤解決方法(下面的)]]。

# A WordPress developer (which could be you) decides to fix the bug. The developer may choose to take responsibility for the bug by clicking on the ''Accept ticket'' option near the bottom of the ticket, though this is not required. Then the developer figures out how to fix the bug, creates one or more patch files, and uploads them to Trac. See [[WordPress:#Patching Bugs|Patching Bugs (below)]]. Also, if you want to help with fixing bugs, but don't know what bugs to fix, see [[WordPress:#Finding Bugs to Fix|Finding Bugs to Fix (below)]].

#WordPress開發(fā)人員（可能是你）決定解決這個(gè)程序錯(cuò)誤。開發(fā)人員可能選擇通過點(diǎn)擊ticket底部旁邊的''接受 ticket''選項(xiàng)，負(fù)責(zé)解決程序錯(cuò)誤，但是這并不是必須的。然后開發(fā)人員思索怎樣解決程序錯(cuò)誤，創(chuàng)建一個(gè)或者更多的補(bǔ)丁文件，并且將這些文件上傳到Trac。請看看[[WordPress:#Patching Bugs|Patching Bugs (下面的)]]。同時(shí)，如果你想要幫助解決程序錯(cuò)誤，但是不知道要解決哪個(gè)程序錯(cuò)誤問題，請看看[[WordPress:#Finding Bugs to Fix|找到程序錯(cuò)誤來解決 (下面的)]]。

# Members of the WordPress development group (including volunteers) test the patch, to see if it fixes the bug and doesn't break anything else. They add comments and keywords to the ticket to indicate their results. See [[WordPress:#Trac Keywords|Trac Keywords list (below)]].

#WordPress開發(fā)小組的成員（包括志愿者）測試補(bǔ)丁，看看是否能夠解決程序錯(cuò)誤，同時(shí)不會(huì)破壞其它的內(nèi)容。他們給tickets添加評(píng)論和keywords，暗示結(jié)果。請看看[[WordPress:#Trac Keywords|Trac Keywords list (下面的)]]。

# One of the WordPress developers with authority to modify the official WordPress source code (Matt Mullenweg, Ryan Boren, Mark Jaquith or Peter Westwood) ''commits'' the patch to the core code in the SVN repository. They are more likely to do this if the bug and patch has been verified by someone they trust.

##更改WordPress官方源代碼，權(quán)威的WordPress開發(fā)人員(Matt Mullenweg, Ryan Boren, Mark Jaquith 或者 Peter Westwood) ''遞交'' 補(bǔ)丁到SVN資源庫的核心代碼。如果程序和補(bǔ)丁由某個(gè)他們信任的人證實(shí)了，開發(fā)人員更會(huì)這么做。

# Finally, the person who commits the patch sets the bug ticket status  to ''closed'' and the resolution to ''fixed''. See [[WordPress:#Bug Resolutions|Bug Resolutions (below)]].

#最后，遞交補(bǔ)丁的人，將程序錯(cuò)誤ticket級(jí)別設(shè)置為''關(guān)閉的''，將解決辦法設(shè)置為''解決的''。請看看[[WordPress:#Bug Resolutions|程序錯(cuò)誤解決辦法 (下面的)]]。