Development & support versions

simon.whiteley · Post by **simon.whiteley** » Mon Sep 27, 2004 11:01 am

A bit of a general question. What would be the recommended way to organise a vault project so that a support team and a development team can work on the same project, without creating completely separate copy.

After a release of version 1, a bug fix team could continue to work on the code as it was when version 1 was released and release patches.
Meanwhile the development team work towards version 2.

Can the bug fixes be merged into the development code as each patch is released?

I can see there might be several ways of organising this, I am just wondering what other people typically do.

dan · Post by **dan** » Mon Sep 27, 2004 12:05 pm

One suggestion is to use the Branch command when one team is ready to enter maintainance mode, and then use the Merge Branches command to merge the changes back into the trunk.

For example, when you release the code to a project at $/trunk/project, use the branch command to create a $/branch/project/1.0. Both teams can work on both branches, and when you want to merge back changes, use Merge Branches to put $/branch/project/1.0 changes back into $/trunk/project.