On Wed, Aug 27, 2008 at 11:02 AM, kroe <[EMAIL PROTECTED]> wrote: > We have recently switched to the scrum development process, and are forced > to rethink our maven versioning scheme. There will be multiple scrum teams > working with the same code-base. Each team will aim to have a release each > sprint, but occasionally a release will be planned for one sprint but > pushed > back to the next. > > Can anyone reccomend a maven versioning scheme that fits the scrum > development process well?
In your proposal, would the development group identifier be numeric? That'd be awkward, as it would imply that higher-identiers supercede lower ones, in terms of a normal versioning number scheme. If I couldn't avoid this kind of structure altogether (which is my first reaction), I'd be inclined to push most of this information pretty far down in the version identifier. I might end up using something like <release major>.<release minor>.<release patch>-<dev group>.<sprint>.<candidate>. So during the development of product release 1.0, you might be working on 1.0.0-MikesTeam.5-SNAPSHOT, and then put out 1.0.0-MikesTeam.5.1 to QA, followed by 1.0.0-MikesTeam.5.2 if they reject it. I don't have any sense of how you're planning on integrating the work from each team into a comon stream, so I won't talk about that. But at least that way the higher version numbers are still meaningful and useful. I'd stay away from numeric representation of the teams to avoid putting some kind of numeric priority to them that wasn't intended. - Geoffrey -- Geoffrey Wiseman
