I the past I've tried to separate the technical versions from the planning
versions. Some projects do this with code names, but we did with release
numbers. The CI system gave us build numbers, we didn't know in advance
which build would become the release, esp weeks in advance. So when people
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 eac
We have separate working branches for each team. After a version is released
it is merged into the trunk. There is only one current production version
of each application. Our software is developed for internal use so no need
to maintain previous versions.
P'Simer, Dana (Matrix) wrote:
>
>
We are doing something similar. I am guessing that you are putting the various
sprint teams on separate branches and merging them in when you need to create a
combined release. Or are you actually producing alternative versions of you
product?
If the former, then the first blush response migh