软件版本编号遵循哪些规则? [英] What rules does software version numbering follow?

问题描述

我一直在开发一些软件，想给它版本号.

I have been developing some software and want to give it version numbers.

我该怎么做?

有的软件有1.3v1.1这样的两个版本是怎么回事

How is it that some software gets two versions like 1.3v1.1

或者有些有 3 个数字 - 4.0.1

or some have 3 numbers - 4.0.1

这一切背后的方法是什么?

What is the method behind all this?

谢谢.

推荐答案

我看到的常用方法是X.Y.Z，一般对应major.minor.patch:

The usual method I have seen is X.Y.Z, which generally corresponds to major.minor.patch:

• 每当引入一些重大更改时，主要版本号就会发生变化.例如，对软件包进行大的或可能向后不兼容的更改.
• 当引入新的次要功能或推出一组较小的功能时，次要版本号会发生变化.
• 当新版本的软件发布给客户时，补丁号会发生变化.这通常用于小错误修复等.

其他变体使用内部版本号作为附加标识符.因此，如果您有许多在版本之间进行测试的修订，则可能会有大量的 X.Y.Z.build.我使用了几个按年/月或年/发布标识的包.因此，2010 年 9 月发布的版本可能是今年的第三个版本的 2010.9 或 2010.3.

Other variations use build numbers as an additional identifier. So you may have a large number for X.Y.Z.build if you have many revisions that are tested between releases. I use a couple of packages that are identified by year/month or year/release. Thus, a release in the month of September of 2010 might be 2010.9 or 2010.3 for the 3rd release of this year.

版本控制有很多变体.这一切都归结为个人喜好.

There are many variants to versioning. It all boils down to personal preference.

对于1.3v1.1"，这可能是两个不同的内部产品，可能是一个与主要产品不同的共享库/代码库；可能表示主产品版本为 1.3，内部库/包版本为 1.1.

For the "1.3v1.1", that may be two different internal products, something that would be a shared library / codebase that is rev'd differently from the main product; that may indicate version 1.3 for the main product, and version 1.1 of the internal library / package.

这篇关于软件版本编号遵循哪些规则?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！