您如何对项目进行版本控制？ [英] How do you version your projects?

问题描述

我了解Microsoft在对其产品进行版本控制时使用此模板：Major.Minor.Build.Revision。

I understand that Microsoft uses this template when versioning their products: Major.Minor.Build.Revision.

当开发人员想要表明软件上有很大的变化并且不能假定向后兼容时，将对主要内容进行更改。也许已经完成了代码的重大重写。

Major is changed when the "developers" want to show that there is a big change in the software and backward compatibility cannot be assumed. Maybe a major rewrite of the code is done.

次要数字代表了向后兼容的显着增强。

Minor number represents a significant enhancement with the intention of backward compatibility.

内部版本号是一个小的更改，例如重新编译相同的源。

Build number is a small change, for example a recompilation of the same source.

修订版用于修复安全漏洞，并且应该可以完全互换。构建和修订都是可选的。此信息基于 MSDN版本类。

Revision is used to fix a security hole and should be fully interchangeable. Both Build and Revision are optional. This information is based on MSDN Version Class.

如何版本化项目以及为什么要用这种方式版本化项目？

How do you version your projects and why do you version them this way?

推荐答案

我们通常在我工作的地方做major.minor [.maintenance [.build]]，但每个项目似乎有所不同。

We generally do major.minor[.maintenance[.build]] where I work, but it seems to vary a little per project.

Major /小调与您提到的相同。对于小型（错误）修复程序，维护工作将会增加，并且每次构建服务器运行时都会进行构建。

Major/minor the same as you mentioned. maintenance would be incremented for small (bug) fixes and build for each time the build server runs.

这篇关于您如何对项目进行版本控制？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！