StarTeam View / Branching Approach

Question

We are looking for tips on our StarTeam configuration. We have a project that is used by two main customers. We use a common code base, but we want to be able to do development for one client at a time. Does anyone know the best way to do this is to use StarTeam?

I would think that you want to do something like this:

->Main branch (1.0)
-->Cust #1 Release (1.1)
-->Cust #2 Release (1.2)

As stated in 1.1, you should merge this code into 2.0. The same goes for 1.2. Then you will create 2.1 or 2.2.

It makes sense? Just looking for some common sense configuration management solutions that will work for our scenario and will work easily with StarTeam.

Thanks.

Refresh . I found the ST best practice guide , which provides useful information on this subject (see chapter 5). Recommendations are built into the use of Craig ST (see below). Please note that this guide was published in December 2003.

Answer 1

You may not want to hear this, but there is no better way. Having said that, I will tell you what we are doing.

. , , , , . .

, . , , :

• , , - , , , .
• , , , .

(1) , , "" > "" , , . (2) ( ) ( , , ), .

,, . , , .

, , . / StarTeam . ( 2005 , , .)