Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.
由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。
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.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
If it's not possible to commit the merged code back to the trunk frequently, test runs can determine if any merge conflicts will occur so that merges are less painful when they are committed.
如果无法经常将代码合并到主干的话，可以运行测试，这样就能够确定是否会发生合并冲突，从而使实施合并没有那么困难。
Developers integrate their code into the trunk as often as possible — typically every few hours — while making sure that all the unit tests pass.
开发人员应当尽可能频繁地把他们的代码集成进主干——典型的是几小时一次，同时还要确保所有单元测试都能通过。
When a team develops in parallel, it's important to merge code back to the mainline (trunk) as often as feasible.
团队进行并行开发时，一定要以最高的频率将代码合并回干线(即主干)。
Note that "release to trunk" doesn't mean that we are copying the code for one specific story to trunk. It means we are copying everything from work to trunk, i.e. doing a complete synchronization.
注意“发布到主干”并不是说我们仅把某个故事的代码直接拷贝到主干中，而是意味着所有的工作拷贝到主干中，做一次完整的同步。
Unless you absolutely have to, a good practice to follow is not to compile software off of trunk in active development, as you might be put in a situation of fixing broken code yourself.
除非在不得已的情况下，否则最好不要对处于活动开发阶段的版本进行编译，因为这样做，您将需要自己动手修复有问题的代码。
When a number of developers work on a single project it's important to make sure that the latest version of the code in the version-control system (the trunk) will always build.
当有许多开发人员在同一个项目上工作时，重要的就是要确保构版本控制系统中代码的最新版本一直被构建。
The code is open source, downloadable, under the name Chromium OS and Google is going to use the same code trunk as everybody else, but their product will be most likely called Chrome OS.
代码是开源可下载的，在ChromiumOS名下，Google也和每个人一样使用着同样的代码主干，不过其产品叫做Chrome OS。
So where do I check in code that I believe is done, but need to verify before checking in to the trunk?
那我应该向何处检入我认为已经完成、但是在检入主干前需要进行验证的代码呢？
So at any given moment, there may be new code on the trunk that I don't know about.
所以在任何给定的时刻，在主干上都可能有我不知道的新代码。
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.
当有人考虑从工作分支向主干发布代码时，要触发该手工测试，以检查故事是否“完成”。
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.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
Assuming the trunk contains source code of released software, the first task is to create an SVN tag based on the trunk. Listing 3 is an example of how to create this release tag.
假设主干包含已发布的软件的源代码的话，第一个任务就是要依据主干创建一个SVN标记。
Expand the trunk and choose the subclipse folder, then click Finish to check out your own copy of the subclipse project's source code.
展开trunk选中subclipse文件夹，然后单击Finish即可检出您自已的subclipse项目的源代码副本。
Merb’s source code repository trunk - A view of Merb’s official git repository at github.com.
Merb的源码repository- github.com上Merb的官方源码repository.
Merb’s source code repository trunk - A view of Merb’s official git repository at github.com.
Merb的源码repository- github.com上Merb的官方源码repository.
应用推荐