源代码控制与修订控制? [英] Source control vs. Revision Control?

问题描述

存储源代码版本(如 SVN 或 TFS)的系统的正确名称是什么?

Which is the correct name for a system which stores versions of source code, like SVN or TFS?

我一直称其为源代码控制，但维基百科之类的地方称其为版本控制?

I've always called it source control, but places like Wikipedia calls it revision control?

为了让这种更复杂的网站同时拥有两个标签?

To make this more complicated sites like this one have a tag for both?

推荐答案

• 修订控制 是更通用的术语，用于源代码控制工具和其他工具(Word、OpenOffice 等).它引用了一个版本.

  • Revision Control is the more generic term, used for source-control tools but also for other tools (Word, OpenOffice, ...). It references a version.

    源代码控制提供带有分支和合并功能的修订控制，但并非在所有修订工具中都可用(Word 不是源代码控制，但提供修订控制功能)

    Source Control offers revision control with branching and merging which are not always available in all revision tools (Word is not a Source Control, but offer revision control features)

    版本控制是比源代码控制更通用的术语，因为它管理任何东西(源代码或二进制文件，或任何类型的文档)的版本

    Version Control is a more general term than Source Control in that it manages version of anything (sources or binaries, or any kind of documents)

    注意:SCM 代表源代码管理，也代表软件代码管理，以反映相同的想法(不仅仅是源"被管理).
    Plus SCM 引入了文件组之间的依赖关系的概念.
    并且它还可以包含导致变更请求系统的变更生命周期的概念(开始变更、关闭变更……).

    Note: SCM stands for Source Code Management, but also for Software Code Management, to reflect the same idea (not just "sources" are managed).
    Plus SCM introduces the notion of dependencies between group of files.
    And it can also includes the notion of change lifecycle (start a change, close a change, ...) which leads to change request system.

    这篇关于源代码控制与修订控制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！