你是怎么做到的版本编号在敏捷项目？ [英] How do you do version numbering in an agile project?

问题描述

目前，我们使用以下版本编号方案，为我们的C＃WinForms项目：

Currently, we're using the following version numbering scheme for our C# winforms project:

主要版本，次要版本，迭代次数。 构建一个迭代中的第

"Major Release"."Minor Release"."Iteration Number"."Build Number within that Iteration"

我们希望能够仅通过查看版本号，以确定迭代中的迭代次数和内部版本号。

We wanted to be able to identify the iteration number and the build number within that iteration just by looking at the version number.

在过去，我们做了一些这样的：主要版本，次要版本，序列版本号1.0。例如，4.0.648就意味着有648建立自1.0 - 但这些信息是相当无用和传闻，这就是为什么我们改变以反映迭代和迭代内建立

In the past, we had done something like:"Major Release"."Minor Release"."Sequential Build Number from 1.0". For example, "4.0.648" would mean there were 648 builds since 1.0 - but this information is fairly useless and anecdotal, which is why we changed to reflect iterations and builds within iterations.

因此，考虑这个新版本的敏捷编号，我们现在在这里不同的产品组想使他们的迭代为我们的项目变更的问题。在这种情况下，版本号将没有任何意义，因为它们的迭代和建立号码不对应。例如，我的项目的最后一个版本是1.0.5.1指示迭代5.第一版本现在这个其他项目，在它的第三次迭代想修改我的项目和重建家园。

So considering this new agile version numbering, we now have the problem where a different product group would like to make changes in their iteration for our project. In this instance, the version number would not make sense, because their iteration and build numbers do not correspond. For example, my project's last build was 1.0.5.1 indicating the 1st build of iteration 5. Now this other project that in it's 3rd iteration would like to make changes to my project and rebuild.

我应该如何这种情况应付呢？你是怎么做到的版本号在你的敏捷项目？

How should I cope with this situation? How do you do version numbering in your agile project?

推荐答案

我跟踪敏捷项目的迭代，而不是软件项目的迭代。如果起步较晚方项目另一个项目后加入会因此初始化与当前的敏捷项目的迭代，并且不会有任何偏差。

I track the agile projects' iteration, not the software projects' iteration. If a late starter side project joins after another project it will therefore init with the current agile project iteration, and there will be no misalignment.

它不应该是可能的敏捷项目的域之外的技术项目与域内的项目进行交互。这将是该进程的PM故障，并应在所有情况下的共享代码库与分支使用被淘汰，要修补到主干作为该项目建成后的净化步骤。

It should not be possible for a technical project outside of the agile project's domain to interact with a project within the domain. That would be a PM failure of the process and should be eliminated in all cases where a shared code base is in use with branching, to be patched into the trunk as a cleanup step after the project completion.

这篇关于你是怎么做到的版本编号在敏捷项目？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！