将针对前一个迭代中所提出的缺陷的修复包整合到FS b中。
Integration of fixes for defects raised in the previous iteration into FSB.
本文讨论这些因素，致力于使用性的恢复和表面缺陷的修复，对于超载引起的损坏则不适用。
The factors discussed address the restoration of serviceability and the correction of cosmetic defects and are not applicable to failures resulting from overloading.
因此，除非在实现，用户接口设计等方面有重大变化，通常情况下仅仅校验缺陷的修复。而性能测试和压力测试又属例外情况。
Therefore normally only defect fixes are verified for most cases unless there are major changes in implementation, UI design etc... Exceptions can be performance and stress testing.
论文采用钢试件高温模拟方法对热加工过程中易引起大型锻件内部探伤超标的孔洞型缺陷、夹杂性裂纹等缺陷的修复规律进行了探讨。
The principle of the internal faults (cavities and cracks originated from inclusion) recovery was investigated in the plastic deformation by using the method of physical modeling at high temperature.
该委员会资深共和党参议员迈克·克拉波说道：“这一结果将是朝着修复我们有缺陷的住房体系迈出的有力一步。”
"The result," said Mike Crapo, the ranking Republican senator on the committee, "would be a strong step forward to fixing our flawed housing system."
宁愿延期六个月推行消费税，也不愿(采用其它方案而)冒先天缺陷的险，今后那将难以修复。
It would rather delay the GST by six months than risk birth defects that would be hard to fix later.
另一个问题是付费用户是否能影响缺陷修复的优先级？
Another question is whether paying customers can influence the priority of bug fixes?
在计划一个发布版本时，项目识别出了团队计划在发布版本中修复的缺陷的数量。
In planning a release, the projects identified n-number of defects that teams planned to fix in the release.
但是如果您的缺陷积压是庞大的，那么将它们全部修复是不是合适的呢？
But if your defect backlog is enormous, is it even wise to necessarily fix it all?
搜索，修复，和解决缺陷的过程又叫做缺陷价值链。
The process of finding, fixing, and resolving defects is known as the defect value chain.
当缺陷被修复和评审的时候，我们经常为缺陷自圆其说。
When defects are triaged and reviewed, we often explain away the reasons for the defect.
所以在使用CLM的假设性范例之中，修复一个缺陷的工作量从4.75个小时降低到3.25个小时，而消耗量从12个小时降低至不超过2个小时。
So in our hypothetical example using CLM, the effort to fix a defect is reduced from 4.75 hours to 3.25, and the waste is reduced from 12 hours to less than 2 hours.
尽量不要试图在这个阶段修复体系结构的缺陷。
海峡两岸的情况都是如此，多数热情的欧盟一体化支持者们实际上在寻找着在自家修复缺陷的方法。
The same is true across the Channel, where the most ardent pro-Europeans are actually seeking to fix a defect at home.
经验证明，在早期阶段发现存在的缺陷，可以使得修复它们成本更低，进而降低IT运作的成本。
Experience shows that catching defects early makes them cheaper to fix, helping you reduce your IT operating costs.
此缺陷将会在SpringRoo的后续版本中修复。
This defect will be fixed in a future release of Spring Roo.
CommunityEdition还包括很多其他缺陷修复，并拥有IBM提供的世界级支持。
Community Edition also includes many other defect fixes, and receives world-class support from IBM.
精心处理“缺陷修复”过程从而避免重新修复的缺陷(请看图12)。
Refine the "defect fix" process to avoid the refixed defects. (See Figure 12.)
缺陷发现以及修复趋势，实际的与期望的。
在许多方面，Windows7并没有彻底脱离Vista，但是更多的是试图去修复Vista的主要缺陷。
In many respects, Windows 7 isn't a radical shift from Vista, but is more of an attempt to fix Vista's main flaws.
到目前为止，开源的开发者通过查询s can上的结果，已经修复了超过8000个的缺陷。
So far over 8000 defects have been fixed by open source developers looking at the Scan results.
举例来说，您可以指定直到修复恶劣所有最严重的缺陷之后测试才是完成的。
For example, you might specify that testing is incomplete until all of the most severe defects have been fixed.
到某个日期为止重新测试允许团队修复那些额外的缺陷。
Retesting by a certain date allows the teams to fix those additional defects.
每个迭代将拥有一个开发包，一些新的特性或场景加入其中并且根据现有场景的缺陷也得到修复。
Each iteration will encompass a development package in which some new features or scenarios are added and some defects against existing scenarios are fixed.
如果您遇到了评审代码以找到缺陷的所有问题，那么修复它们就变得顺理成章了！
If you're going to all of the trouble of reviewing code to find bugs, it certainly makes sense to fix them!
因为相同的构建工件已经在各个站点被构建，任何失败的测试或者被修复的缺陷都能够在任何站点重现，使调试和错误更正更简单。
Because the same build artifacts have been built at each site, any failed test or identified defect can be reproduced at any site to facilitate easier debugging and error correction.
缺陷修复任务成为团队优先级最高的任务。
The defect task becomes the highest priority task for the team.
通过在引入了缺陷的构建中找到这些缺陷，可以尽可能低成本地进行确定，并且减少了相互依赖的缺陷修复的复杂链的风险。
By finding these defects on the build in which they were introduced, the fixes can be provided as cheaply as possible, and the risk of complex chains of interdependent fixes is reduced.
通过在引入了缺陷的构建中找到这些缺陷，可以尽可能低成本地进行确定，并且减少了相互依赖的缺陷修复的复杂链的风险。
By finding these defects on the build in which they were introduced, the fixes can be provided as cheaply as possible, and the risk of complex chains of interdependent fixes is reduced.
应用推荐