Sometimes, the risk level has nothing to do with the "health" of the code, but because the feature (or configuration) in question is so critical to the product in general or to specific customers.
有时候，风险级别与代码的“健康”无关，但是因为正在讨论的特性（或配置）一般对产品或具体的客户来说是关键的。
By focusing on just the individual feature or component, we are unintentionally making code decisions that negatively impact the overall flow and usability of the product.
通过聚焦于个别的特性或者组件，我们不经意的做了一些代码的决定，这对产品的全面流程和可用性产生了消极的影响。
In earlier product cycles, we'd used a proprietary system for tracking bugs, another one for storing code, and some combination of bug reports and spreadsheets to track feature progress.
在早期的产品开发周期中，我们用专门的系统去跟踪缺陷，另外一个系统存储代码，还有缺陷报告和报表去跟踪特性的进度。
A strategy we used to pursue the "test code early and often" best practice was to involve developers in both feature verification and product verification (system-level) testing.
我们曾经提到的策略“尽早并经常地测试代码”是一项为开发者提出的最佳实践，无论是在特性验证还是产品的验证(系统级)测试中。
Verify that the new server has the correct product code and feature release level assigned.
校验新服务器已经有正确的产品号码和关联的产品特性。
Verify that the new server has the correct product code and feature release level assigned.
校验新服务器已经有正确的产品号码和关联的产品特性。
应用推荐