您喜欢的产品版本号样式是什么?为什么? [英] What is your preferred style of product version number and why?

查看:38
本文介绍了您喜欢的产品版本号样式是什么?为什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是 Major.Minor.Release - IBM 风格(例如 1.2.3)吗?是年吗?(Windows '98)还有什么?

Is it Major.Minor.Release - IBM style (eg. 1.2.3)? Is it the Year? (Windows '98) Something else?

参考:http://en.wikipedia.org/wiki/Versioning

目前我使用Major.minor.release.internal-release

Presently I use major.minor.release.internal-release

示例01.12.02.19

Example 01.12.02.19

对于下一个产品,我想让它变得更简单版本构建

For the next product, I was thinking of making it simpler Version-Build

示例v1-b22

在我最终确定之前(因为我将不得不在产品的余生中接受我的决定)我想获得尽可能多的观点.

Before I finalize ('cause I will have to live with my decision for the rest of the product's life) I want to get as many points of views as I can.

非常感谢!

推荐答案

[major].[minor].[patch]

例如:2.0.4

当产品有许多新的主要功能时,Major 会增加,当添加一些次要功能时会增加次要,如果没有添加新功能,但补丁或安全问题已经被修补,则补丁会增加.

Major is incremented when the product has many new, major features, minor is incremented when a few minor features are added, patch is incremented when no new features are added, but bug fixes or security issues have been patched.

我更喜欢这个,因为它简单、高效,而且大多数人无需解释就能理解这些版本号,即使是非开发人员.

I prefer this because it's simple, efficient, and most people understand these version numbers without explanation, even non-developers.

这篇关于您喜欢的产品版本号样式是什么?为什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆