正确获取软件版本号. v1.0.0.1 [英] Getting software version numbers right. v1.0.0.1

问题描述

我在线分发软件，总是想知道是否存在适当的方法来更好地定义版本号.

I distribute software online, and always wonder if there is a proper way to better define version numbers.

让我们假设答案是A.B.C.D.您何时增加每种成分?

Let's assume A.B.C.D in the answers. When do you increase each of the components?

您是否使用了其他任何版本号技巧，例如D mod 2 == 1意味着它仅是内部发行版?

Do you use any other version number tricks such as D mod 2 == 1 means it is an in house release only?

您是否有带有自己版本号的beta版本，或者每个版本号都有beta版本?

Do you have beta releases with their own version numbers, or do you have beta releases per version number?

推荐答案

我开始喜欢某些应用程序(例如Perforce)使用的Year.Release [.Build]约定.基本上，它只是说出您发布的年份以及该年内的顺序.因此，2008.1将是第一个版本，如果您再发布一个月或三个月后，它将发布到2008.2..

I'm starting to like the Year.Release[.Build] convention that some apps (e.g. Perforce) use. Basically it just says the year in which you release, and the sequence within that year. So 2008.1 would be the first version, and if you released another a months or three later, it would go to 2008.2.

此方案的优点是没有隐含的发布数量级"，您可以在其中争论某个功能是否足够主要以保证主要版本的增加.

The advantage of this scheme is there is no implied "magnitude" of release, where you get into arguments about whether a feature is major enough to warrant a major version increment or not.

可选的附加功能是标记内部版本号，但这往往仅出于内部目的(例如添加到EXE/DLL中，以便您可以检查文件并确保正确的内部版本).

An optional extra is to tag on the build number, but that tends to be for internal purposes only (e.g. added to the EXE/DLL so you can inspect the file and ensure the right build is there).

这篇关于正确获取软件版本号. v1.0.0.1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！