其他开发团队如何处理版本号? [英] How do other development teams approach version numbers?

问题描述

我们的应用程序已经相当成熟，因此我们已经到了 16 版本.但是，这可能会给人一种感觉，该软件是旧的，脱节(20+ 版本有多少商业应用程序??)

Our application is quite mature, and thus we are up to version 16. However, this can give the impression that the software is old and out of touch (how many commercial applications are there with a version 20+??)

显然，版本号非常随意——其他人使用什么?我非常喜欢 Ubuntu 的month.date 方法，但我想看看人们使用的其他策略.

Obviously, version numbers are quite arbitrary - what do other people use? I quite like the Ubuntu approach of month.date, but I'd like to see what other strategies people use.

推荐答案

我们倾向于使用 1.20.5 之类的东西，在您的情况下，20 是相当高的发布"号或其他东西.

We tend to go with something like 1.20.5, where the 20 is, in your case, the fairly high 'release' number or something.

当我们用不同的实现完全重写一个产品时，它就会变成 2.0.0，依此类推.

When we completely re-write a product in a different implementation, it becomes 2.0.0, and so on.

这也意味着测试版可以是 0.2.3，例如.

It also means that the beta versions can be 0.2.3, for example.

这篇关于其他开发团队如何处理版本号?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！