4 messages in com.perforce.perforce-user[p4] Depot Structure?
FromSent OnAttachments
Stéphane Bouchard22 Oct 2003 06:49 
Noel Yap22 Oct 2003 08:29 
Eivind Hagen22 Oct 2003 09:50 
Paul Goffin22 Oct 2003 11:20 
Subject:[p4] Depot Structure?
From:Stéphane Bouchard (sbou@solvision.net)
Date:10/22/2003 06:49:51 AM
List:com.perforce.perforce-user

Hi,

For the deployement of our new perforce solution, we have two possibility for the depot structure. Please note that we have a product call 'library' that is use by all our product. This 'library' is all our dll and it's the primary reason why I'm not sure about the depot structure. When we branch a product, we need to branch the 'library' too. Can you give me your opinion about the two structure. Don't forget to give me good argument, so I will can use that argument to convince the developer group.

Thank's

First Structure: ================ In the first structure, we have one mainline for all the products. So when we branch, all the products will be branched even product that we do not need. This structure is a option because the branch is a whole that include de 'library' and the product. The rest could be just unshow in the client workspace.

products-+-main-+-library + +-product_A + +-product_B + +-releases-+-product_A-+-release_1-+-library + + + +-product_A + + + +-product_B + + + + + +-release_2-+-library + + + +-product_A + + + +-product_B + + + +-product_B-+-release_1-+-library + + + +-product_A + + + +-product_B + + + + + +-release_2-+-library + + + +-product_A + + + +-product_B + +-tasks-+-product_A-+-task_1-+-library + + + +-product_A + + + +-product_B + + + + + +-task_2-+-library + + + +-product_A + + + +-product_B + + + +-product_B-+-task_1-+-library + + + +-product_A + + + +-product_B + + + + + +-task_2-+-library + + + +-product_A + + + +-product_B +

Second Structure: ================= In the second structure, we have a mainline for each products including the 'library' product. So when we branch, we have to make to branch, on for the product and another for the 'library' product. This structure is a option because we only branch what we need to branch. But we have to deal with two branch for each release or task.

products-+-library-+-main + + + +-releases-+-release_A_1 + + +-release_A_2 + + + + + +-release_B_1 + + +-release_B_2 + + + +-tasks-+-task_A_1 + + +-task_A_2 + + + + + +-task_B_1 + + +-task_B_2 + +-product_A-+-main + + + +-releases-+-release_A_1 + +-releases-+-release_A_2 + + + +-tasks-+-task_A_1 + +-tasks-+-task_A_2 + +-product_B-+-main + + + +-releases-+-release_B_1 + +-releases-+-release_B_2 + + + +-tasks-+-task_B_1 + +-tasks-+-task_B_2