每个数字在软件版本中(例如1.7.1.0)意味着什么? [英] What every digit means in software version (1.7.1.0, for example)?

问题描述

每个数字在软件版本中意味着什么? (例如1.7.1.0) 您如何计算版本?

What could every digit mean in software version? (for example, 1.7.1.0) How do you numerate your versions?

谢谢.

推荐答案

每个供应商之间的确存在差异.最常见的是(按顺序):

It differs from vendor to vendor really. Most commonly, they are (in order):

• 主要版本号
• 次要发布号
• 维护版本号(仅错误修正)
• 如果完全使用:内部版本号(或源代码管理修订版号)

1.7.1.0将是产品1.7版本的第一个维护版本.

1.7.1.0 would this be the first maintenance release to the 1.7 version of the product.

即使定义主要版本和次要版本之间的区别也很困难.主要版本通常包含重要的新功能.或者供应商只是希望人们再次为产品付款.次要版本可能包含修复程序和新功能，但通常没有突破性的内容.

Even defining what the difference between a major and minor release is, is difficult. Major releases normally include significant new features. Or the vendor just wants people to pay for the product again. Minor releases may include fixes and new features, but usually nothing ground breaking.

一些公司使用次要版本位来区分alpha/beta版本和最终版本.奇数表示预发行，偶数表示决赛. 1.7将是即将发布的1.8版本的测试版.不过，这种习惯越来越少.

Some companies use the minor release bit to differentiate between alpha / beta releases and final releases. Odd numbers being pre-releases and even numbers being finals. 1.7 would be a beta of an upcoming 1.8 release. This habit is becoming less and less common though.

内部版本号随每个发行版而增加，无论更改有多小.每次运行时，它都会由构建过程自动递增.许多版本从未公开发布过，但是它们可以使QA轻松地唯一标识该软件的版本，从而有助于管理软件的生命周期.

Build numbers increment with every release, no matter how minor the changes might be. It is automatically incremented by the build process, every time it runs. Many builds are never see publicly released, but they can help in managing the life cycle of the software, by making it easy for QA to uniquely identify a version of the software.

这篇关于每个数字在软件版本中(例如1.7.1.0)意味着什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！