Branching limitations - is there any in vault?

fresh_ant · Post by **fresh_ant** » Thu Nov 24, 2005 1:19 pm

Hi,

I am trying to evaluate version controls systems (VSS, Vault, CVS) to find out which one i need to use for my web based application which is basically a product.

I am mainly interested to know how many branches are possible in vault, since ours is a product, we sell it to a lot of customers, and for each client we do a bit of customization yet retaining the bulk of the main source code.

So i would like to know if any one has been using Vault to store their product source code and if so how many branches have you made.

Or is there any best practice which source gear recommends to do version control for products.

That is we have different vertical versions - namely 1.0, 1.1, 1.2, .............2.X etc and at the same time for each version horizontally we need to keep track of customizations for different clients.

That is Version 1.1 for client A is different from version 1.1 for client B since we may use different images or colors inside the source code for each client. Since all these need to sit inside the SCM.

Meaning Version 1.1 of the code is different for client A as compared to client B, in version 1.1. i may use the clietns logos and images for client A and for client B i may use their logos and color pallette.

Any information in this regard would be appreciated.

does any one out here do have the same problems of both horizontal and vertical nightmare of managing source code?

Thank you
Prashant.

Post by **jclausius** » Mon Nov 28, 2005 9:53 am

Prashant:

I would create a main trunk which would contain the latest version of your project.

At each release, create a main branch which represents version 1, 2, 3, etc. If you want to start with the same code base, you may want to pin the branch or use snapshot.

In any case, as each customer starts making change requests, branch the branch for each customer. This way you have the flexibility for merging customer changes up/down between each customer branch. Additinally, and you can merge any changes from each "main branch" up into the current trunk.

HTH