Use Version-Control and Change-Tracking tools.
采用版本控制和变更追踪工具。
Committing all files to a version-control repository.
把所有文件提交给一个版本控制存储库。
You should increase the build interval for remote projects to reduce the load on their version-control repositories.
可以提高远程项目的构建间隔，以减轻它们的版本控制仓库的负担。
Pattern: all files are committed to version-control repository - in the deployment context, all of the configuration files and tools.
模式：所有文件都被提交给版本控制存储库—在部署上下文中，这是指所有配置文件和工具。
The key is to have some form of version control and access management to the architecture structure.
关键是要对体系结构的结构采用某种形式的版本控制和访问管理。
Clearly, semantic integration introduces notions of semantic consistency, which have implications for configuration management and version control.
明显地，语义集成引入了语义一致性的概念，这暗示了配置管理和版本控制。
The ignore file does not omit files already under version control; it omits only those not yet in the repository.
忽略文件并不排除已经置于版本控制之下的文件；它只排除存储库中还没有的文件。
On the other hand, version control systems typically require less storage space than other types of file systems.
另一方面，与其它类型的文件系统相比，版本控制系统通常需要的存储空间更少。
Using either approach, you do not have the rich history capabilities available with a version control system.
不管使用何种方法，都不能像版本控制系统那样提供丰富的历史特性。
Requirements management tools, source code management, and version control software have had good support for multiple users for years.
需求管理工具、源代码管理和版本控制软件对多用户的支持已经有很多年了。
Many of the capabilities for capturing rich history information have been around for years with version control systems.
许多年前，版本控制系统就已经提供用于获取丰富的历史信息的许多功能了。
For starters, imagine that you have your project in the source code version control system, such as CVS.
对于初学者来说，设想一下，项目放在源代码版本控制系统中，例如CVS。
It adds views as necessary to allow the user to interact with whatever version control system (if any) is being used.
它根据需要添加视图，以允许用户与所使用的任何版本控制系统(如果有的话)交互。
Again you might wonder why you should put your development and Integration schemas under version control.
您可能再一次会想到，为什么要将开发与集成方案置于版本控制之下呢。
These products provide not only version control, but also change tracking, workflow support for change management, and full asset management.
这些产品不仅提供了版本控制，而且提供了变更跟踪，支持变更管理的工作流以及全面的资产管理。
This paper describes an example of how to handle version control in an agile environment with multiple teams.
本文讲述了关于如何在敏捷的环境中与多个团队共同进行版本控制工作的实例。
Handling changes, managing version control, upgrading designs, and fixing problems all require a tremendous amount of effort.
处理变更、管理版本控制、更新设计和修复问题都需要付出大量的努力。
We have even seen customers manage all their requirements in spreadsheets and use CVS for version control.
我们甚至看到过客户在电子表格中管理他们的所有需求，并将CVS用于版本控制。
Every time a team member commits modifications to a version control repository, the code has changed.
每当团队成员向版本控制存储库提交更改时，代码就会发生改变。
Without version control, you would have to be much more cautious, move more slowly, and generally be less productive.
如果没有版本控制，您必须极为慎之又慎，缓慢地推进，总而言之，生产力会更低。
When you are using a version control system, you need to put both files into the version control system.
当您在使用版本控制系统时，您需要将两个文件都放置到版本控制系统中。
This approach has many names: configuration management, change management, source code control, library control, version control and so on.
这种方法有很多名称：配置管理、变更管理、源代码控制、库控制、版本控制等等。
Once a change is deployed, the resources are usually committed to the version control system and tagged or labeled.
部署变更之后，资源通常被提交到版本控制系统，并被赋予一个标记或标签。
All code had to be reviewed before it was checked into the team's version control software.
在检入到团队的版本控制软件之前，所有的代码都必须进行评审。
SCM deals with version control, workspace management, software integration, software builds, software deployment, and release processes.
SCM涉及到版本控制、工作空间管理、软件集成、软件构造、软件部署和发布过程。
Screen mockups are saved in XML format and can be easily stored under version control, compared and merged.
窗体原型以xml的格式保存，所以可以容易的进行版本控制，对比和合并。
This makes obvious sense when considering the level of control the developer has on version control.
考虑到开发商对版本控制的控制水平，这么做是很合理的。
It's easy to pull a report from version control so audit can verify that changes were authorized.
这样就很容易从版本控制工具中得到报表，从而审计会认为这些变更是被授权了的。
You won't necessarily run every test defined with every source change applied to your version control repository.
在将每个源变更应用到版本控制库中时，不必运行每个定义的测试。
Put this file under version control, too, to help collaborators avoid adding spurious files to the repository.
把这个文件也置于版本控制之下，这有助于避免合作者在存储库中添加伪造的文件。
应用推荐