确保代码分支在正确的方向上。
在多代码分支上进行并行开发时，自动化就更加有用了。
Automation is even more useful when doing parallel development, working on various branches of the code.
开发人员可以在主代码分支之外自由地试验新概念，而不会影响稳定的配置。
Developers can have the freedom to flesh out concepts outside of the main code branch without impacting stable configurations.
提供有关对团队项目中受版本控制的代码分支进行分支和合并的信息。
Provides information about branching and merging versioned code branches in team projects.
随着时间推移，这个意愿已经形成了具有真正商业价的、让Linux变得更加无处不在的、更加灵活的代码分支。
As it turns out, that desire has led to code branches that have been of real commercial value and that have made Linux ever more ubiquitous and flexible.
由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。
Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.
另一个选项是通过从选定的CVS资源库分支导入代码来创建新的工作台项目。
Another option is to create a new workbench project by importing code from the selected branch of the CVS repository.
如果编译器知道这种预测信息，就可以围绕最可能执行的分支生成最优的代码。
If the compiler has this prediction information, it can generate the most optimal code around the branch.
“仆人”不能向工作分支中检入不可发布的代码。
A Servant may never check in unreleasable code on the work branch.
即便无法访问这些分支，但只要对仓库进行克隆就可以获得这些代码。
Even if those branches are never accessed, just cloning the repository can bring down infringing code.
请注意因为我在每个分支中只有一行代码，显然地我省略了什么？
And notice because I have just one line of code inside of each of these branches, what have I clearly omitted?
这个工具分析内核代码的覆盖率，并报告哪些行、函数和分支被覆盖以及它们被访问了多少次。
This tool analyzes the coverage of the kernel, and reports what lines, functions, and branches are covered and how many times they were hit.
规则：经常从工作分支向主干合并代码，例如每完成一个故事之后。
Rule: Merge from your work branch to the trunk on a regular basis, for example whenever a story is done.
请记住：删除分支的目的在于对代码进行向量化。
Remember that the point of removing the branch was so that you can vectorize the code.
当有人考虑从工作分支向主干发布代码时，要触发该手工测试，以检查故事是否“完成”。
This test is triggered manually whenever someone is considering to publish code from work to trunk, as a way to check that the story is Done.
代码覆盖工具可报告测试覆盖率——以行覆盖或分支覆盖形式表示——它表示测试运行时所涉及的代码量。
A code coverage tool reports test coverage — either in the form of line or branch coverage — that represents the amount of code that is being touched when a test is run.
合并一般是源代码控制系统中的关键方面，在面向分支的VCS尤其常见。
Merges are a key aspect of a source code control system in general and are especially common in a branch-oriented VCS.
最后，请注意函数调用的分支目标并不是启动它的代码，而是.opd入点描述符。
Finally, notice that the branch target for the function call is not the code that starts it, but the.opd entry point descriptor.
规则：每天都从主干向你的工作分支中合并代码。
而且，在大家要求之前，我们已经计划将所有的修改贡献给Lucene；有一些代码已经写入Lucene最新的开发分支，和新的实时版本。
And, before you ask, we're planning on contributing all these changes back to Lucene; some of which have already made it into Lucene's trunk and its new realtime branch.
从核心平台代码创建分支。
当每个方法都有了至少一个测试，使用一个代码覆盖率工具如cobertura为每个分支编写一个测试，直到每一行代码都能够被测试。
Once every method has at least one test, use a code coverage tool, such as Cobertura, to write one test for every branch until each line of code is tested.
Subversion是一个源代码控制系统，它可以跟踪代码库的修改，允许开发人员创建新分支和在单独环境中合并特性开发代码。
Subversion is a source code control system that tracks changes to the code base and allows developers to branch and merge code to work on features in a separate environment.
从工作分支中取得并合并最新的代码，然后检入你的代码。
Merge down the latest from the work branch, and check in your code.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
At that point we can (and should) publish to the trunk, i.e. take all new code on the work branch and copy over to the trunk.
JIT编译器可能生成错误代码，该代码引用或尝试对无效的位置进行分支。
The JIT compiler may produce incorrect code that either references or attempts to branch to an invalid location.
每个分支、循环，或其他逻辑在加入源代码之前都要写出将要执行结果的自动化测试。
Each branch, loop, or other logic added to the source code is preceded by the writing of an atomic test that will exercise that outcome.
在开发人员使用有条件代码时，常常知道最可能执行哪个分支，而哪个分支很少执行。
When working with conditional code, you often know which branch is most likely and which is not.
您可以通过许多方法来测量代码覆盖率：通过评估代码行或语句的覆盖面、条件覆盖面、分支覆盖面等等。
You can measure code coverage in several ways: by assessing line or statement coverage, condition coverage, branch coverage, and so on.
您可以通过许多方法来测量代码覆盖率：通过评估代码行或语句的覆盖面、条件覆盖面、分支覆盖面等等。
You can measure code coverage in several ways: by assessing line or statement coverage, condition coverage, branch coverage, and so on.
应用推荐