决定版本号 [英] Deciding on version numbers
问题描述
重复
你好
所以我最近看到 Groovy 发布到 1.6 版本，在听 Java Posse Podcast 时，他们评论说这个版本中包含了这么多内容已发布2.0.
So I recently saw that Groovy was released to version 1.6 and while listening to the Java Posse Podcast they were commenting how there was so much packed into this release it should have been a 2.0 release.
这让我想到了.版本号是任意的吗?我曾经认为它们是有意义的，但我想不是.只是基于里程碑并将项目设置为项目吗?
That got me thinking. Are version numbers just arbitrary? I used to think they had a meaning but I guess not. Is it all just milestone based and set project to project?
您的团队如何控制您的版本号和版本?
How does your team control your version numbers and releases?
提前致谢
推荐答案
区分用于营销的版本控制和用于技术用途的版本控制.
Distinguish between versioning for marketing and versioning for technical use.
对于营销，答案是:无论您希望客户怎么想."在这种情况下，主要新版本"可能应该伴随一个主要版本号.
For marketing, the answer is: "Whatever you want your customers to think." In that case, a "major new version" should probably be accompanied by a major version number.
另请注意，细心的客户会犹豫是否使用主要"新版本，直到时间过去并且他们已经在测试环境中尝试过.构建更改"版本被认为具有错误修复和其他不需要太多安装过程的小东西.
Also be aware that careful customers will be hesitant to use "major" new releases until time has passed and they've tried it in a test environment. A "build change" release is perceived as having bug fixes and other minor things that don't require much process to install.
对于技术用途，答案是:您想为开发人员编码的任何信息."没有一种正确的方法可以做到这一点.这取决于您的目标.
For technical use, the answer is: "Whatever information you want to encode for developers." There's no one correct way to do this; it depends on your goals.
也许主要"版本意味着可能意味着许多新错误的重大更改".也许每次编译都会出现一个新的构建"编号.也许每晚按日期构建标签是您的版本.您可以根据时间、Scrum 周期、里程碑、功能等等来确定它！
Perhaps a "major" version means "significant changes that might mean lots of new bugs." Perhaps a new "build" number happens on every single compile. Perhaps nightly build tags by date are your version. You can base it on time, Scrum cycles, milestones, features, whatever!
这篇关于决定版本号的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
