RE: Re: Suggested structure?

OK. FYI, I use Master in this example since the repository houses other development streams (and teams) as well. So there's already a "Master0", e.g.

So if I follow you correctly (never a good assumption!) each dev would just check out the repos to the Prod/Dev/Arch level. Thus, not the individual projects.

For a modification, he would create a branch in Dev (using repo-browser?) then do SVN Update? But, won't that pull in all the other projects? (there are hundreds).

e.g. for a new developer:

1. checkout to 2nd level, giving

Master
---- Prod
---- Dev
---- Arch

2. When starting to work on a mod, he wants to do something so that he can see:

Master
---- Prod
-------- project_in_production

3. He'd then branch the production one to work on it, giving:

Master
---- Prod
-------- project_in_production
---- Dev
-------- project in development

4. Code/test/debug, etc.

5. When ready to promote, does a merge-re-integrate?

My problem in understanding is that, at step 2, how can he get the production version of the one project he wants to work on?

I'm concerned that, whenever he runs an SVN Update, he'll get the hundreds of other projects in his WC, taking up bandwidth and disk space. Can that be avoided?

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-18 20:40:20 CEST