WordPress:How does code make it into WordPress

Once you've started contributing to the core code of WordPress, helping with tickets in trac. and carefully crafting patches, you'll soon start to wonder about the process by which code makes its way into the next WordPress release.

你一旦开始帮助处理WordPress核心代码，帮助trac中的tickets，认真仔细地创建补丁，不久你就想知道，代码怎样组合，发行下一个版本的WordPress。

The quick answer is that code makes it into WordPress when one of the team of core developers adds it and no sooner. The developers are busy people, and often with different priorities and different views of WordPress to your own. This can make the process seem like a long and secret one.

答案是当小组的核心成员之间添加补丁，不久代码就将补丁加入WordPress。开发人员都很忙，而且拥有不同的优先权，看待WordPress观点也可能与你不同。这样，WordPress版本升级的过程看起来似乎又长，又神秘。

你可以怎样帮助处理升级

• Your code won't go far without a ticket in trac. Create one.

• 如果在trac中没有ticket，你的代码不会久存。创建一个。

• Clearly define, explain and demonstrate your problem or feature request.

• 清楚地定义，解释，说明你的问题或者功能请求。

• Carefully consider, and take into account advice and feedback given on trac..

• 认真思考trac中提出的建议和反馈..

• Write easily understandable, documented code.

• 编写易懂的，拥有文件证明的代码。

• Consider writing a plugin instead.

• 考虑编写插件替换。

• Appropriate tags in trac help attract appropriate attention.

• trac中标签帮助引起注意。

• Work with and learn from the WordPress community.

• 向WordPress团队学习，与之一起努力。

Finally, don't be disheartened if your code is rejected. Even though WordPress has a strong community, the core developers have the final word in the direction of WordPress.

最后，如果你的代码没有被接受，不要灰心丧气。虽然WordPress有很强大的团队，核心开发人员最终决定WordPress的发展方向。

其它参考

• WordPress:Reporting_Bugs
• November 2007 wp-hackers "How does code make it into core?"
• WP On-going Development Blog

• Reporting_Bugs
• wp-hackers "补丁怎样变为核心代码?"
• WP 正在运行的开发博客