在发布分支上针对缺陷打补丁。
不必每次都创建一个全新的发布分支。
创建一个名为“发布1.0”的发布分支，基于它在发布时的主干内容。
Create a release branch called release 1.0, based on the trunk at the time it was released.
不幸的是，这也意味着SeleniumIDE正式的在主要发布分支中逐步取消对Groovy、Perl和PHP的插件的支持。
Unfortunately, this also means that Selenium IDE is officially deprecating inclusion of the Groovy, Perl and PHP plugins in the main release branch.
由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。
Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.
“仆人”不能向工作分支中检入不可发布的代码。
A Servant may never check in unreleasable code on the work branch.
团队分支是红色的，表示它不太稳定；例如：这个分支通过了单元测试，但是它可能还没有完成集成测试，所以还没有稳定到可以发布的状态。
The team branch is red to highlight that it is less stable, i.e. the stuff on that branch passes the unit tests but it might not be integration tested and might not be stable enough for release.
有些时候，开发团队可能会选择不创建分支，免得会延误发布或导致开发人员瓶颈。
Some may choose not to create branches, which leads to delayed releases and developer bottlenecks.
当有人考虑从工作分支向主干发布代码时，要触发该手工测试，以检查故事是否“完成”。
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.
Allen建议为发布而分支，这也是他偏好的分支策略，同时解释了他为什么会为每个新的发布版本重创数据库基线。
Allen suggests branch For release as his preferred branching strategy, and explains that he re-baselines the database with each new release.
注意我们在发布1.0.0版本时没有必要创建“发布1.0”分支，可以等到问题出现时再做。
Note that we don't have to create the release 1.0 branch when we do release 1.0.0. We can wait until the defect comes up.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
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.
理论上来说，这样做没有问题；因为主干是“完成”分支，而“完成”的定义就是“可发布的”。
Theoretically this should be fine since the trunk is the Done branch and the definition of Done is "releasable".
在这些环境里，分支或流趋向于长的生存期；并且如果你需要将变化集成到多个发布版本，这可能会引起更复杂的集成问题。
In these environments, branches or streams tend to have long lives; and if you need to integrate changes into multiple releases, this may cause more sophisticated integration problems.
订户(而非发布者)可以指定包含通配符的主题名称，这将创建订阅多个主题的单个订阅，如主题层次结构中的某个分支。
A subscriber (but not a publisher) can specify a topic name that contains wildcard characters, which creates a single subscription to multiple topics, such as a branch in a topic hierarchy.
规则：不要在单一分支上合并不同的发布周期。
Rule: Don't combine different release cycles on a single branch.
刚刚发布，并且随着这个版本的发布，IBMGuidedActivityAssistant成为了一种获得充分支持的问题确定工具。
Has just been released, and with this version, the IBM Guided Activity Assistant becomes a fully-supported problem determination tool.
你的经理和项目负责人应经常与你交流以确保你时时记得进度表、合并点、分支名和发布日期。
Your managers and project leaders are expected to talk to you frequently enough to make certain you are aware of schedules, merge points, branch names, and release dates.
如何转换为下个主要发布版本分支？
Equinox 3.5已经部分支持OSGi 4.2了，ApacheFelix在上月初也已经通过了一个测试集(在4.2规范发布前)。
Equinox 3.5 already provided some of the OSGi 4.2 support, and Apache Felix had a passing test set earlier on in the month (prior to the 4.2 spec being passed).
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
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.
感谢所有检验了不稳定分支并让我们不至于发布一个热崩溃的人们。
Thank you to everyone who checked out the unstable branch and helped ensure we weren't releasing a hot break.
在中国人民银行或其分支机构正式发布公告之前，任何机构不得擅自对市场发布相关信息。
No institution may illegally release any relevant information to the market before the PBC or its branch publicizes an official bulletin.
因为主干是“完成”分支，而“完成”的定义就是“可发布的”。
Theoretically this should be fine since the trunk is the Done branch and the definition of Done is "releasable".
因为主干是“完成”分支，而“完成”的定义就是“可发布的”。
Theoretically this should be fine since the trunk is the Done branch and the definition of Done is "releasable".
应用推荐