1·We add the year and month to the namespace as this is the DE facto standard for versioning of namespaces.
我们将年份和月份添加到该命名空间，因为这种做法是命名空间版本控制的事实标准。
2·Of course, the advantage here is that no one has to remember to run queries in the requirements management tool to see what requirements should receive a versioning review.
当然，这里的好处是不用有人必须记得要在需求管理工具中运行查询，来看什么需求应该接受一个版本控制的评审。
3·Using versioning, a copy of the document can be saved before the change occurs.
使用版本控制，在更改发生之前可以保存文档的一份副本。
4·Both of these patterns therefore aid the goals of Canonical Versioning.
因此，二者都有助于规范版本控制目标的实现。
5·On the other hand, if a backward incompatible change is introduced without versioning, existing consumers will no longer work.
另一方面，如果引入无版本控制的不向后兼容变更，现有使用者将不能再工作。
1·The asset management team can extend these as they work closely with the respective communities; specifying the community map, the asset workflows, and the asset versioning policies.
随着资产管理团队与各自的团体合作的密切，它们可以扩展这些内容，指定团体图、资产工作流和资产版本化政策。
2·Another requirement that is often overlooked is the versioning of builds.
另一个常常忽略的需求，是构建的版本化。
3·This means the communities will specify asset versioning, asset workflow, asset types, and classification.
这意味着团体将指定资产版本化、资产工作流、资产类型和分类。
4·Most requirements management tools maintain a history of each requirement, but they do not do versioning.
许多需求管理工具为每一个需求都保持了历史记录，但是并不能实现版本化。
5·The key here is that a consistent asset versioning policy is declared so the repository and its users behave appropriately.
这里的关键在于发布了一致的资产版本化政策，所以存储库及其用户可以适当地工作。