[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Advice on handling common code

From: C M <cmanalyst66_at_gmail.com>
Date: Tue, 8 Jan 2013 10:45:07 -0600

All,

I am setting up a new repository and have a question on how to handle
“common” code. Common refers to code which is shared across the multiple
systems that we deploy.

In addition to the common code, we also have system-specfic software
(custom code).

Given the typical SVN layout, what’s a recommended way to manage this,
especially when creating release tags?

In this model, we include the

/trunk/common_version1/application_1

../../application_2

./../application_3

/trunk/system1/application_1

../../application_2

../../application_3

/tags/system1/Rel_1 [where this may include the system1 apps plus
common_version1/application_1 and application 3]

../system2/application_1

../system2/application_2

../system2/application_3

/tags/system2/Rel_1 [where this may include system2 apps plus
common_version1/application_1, application_2 and application3]

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3041855

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-08 17:45:17 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.