Hi,
On 18 October 2011 20:40, Gerald Britton <gerald.britton_at_gmail.com> wrote:
> 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).
>
No, in that case, you should only check out the projects you are interested
in (each as a separate working copy). Or you work with a 'sparse' working
copy[1]. IMHO using a 'sparse' working copy should only be done by
developers/users that are reasonably experienced with SVN as it takes a bit
of getting used to.
>
> 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
>
>
So, do a checkout of that folder into something like \My
Documents\work\projectX
> 3. He'd then branch the production one to work on it, giving:
>
> Master
> ---- Prod
> -------- project_in_production
> ---- Dev
> -------- project in development
>
> Yes, at the repository side that is correct, the branch can be created by
right clicking on \My Documents\work\projectX and then entering the Dev/...
path and checking the 'switch working copy to new tag/branch'.
> 4. Code/test/debug, etc.
>
> 5. When ready to promote, does a merge-re-integrate?
>
>
Yes.
> 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?
>
>
See comments above.
> 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?
>
> Yes that can and should be avoided. See above.
[1] - sparse working copies are working copies where one or more folders are
suppressed from a chackout and update. These are created by doing an initial
checkout with a depth setting other than 'Fully Recursive'. To learn more
about this, read the TSVN manual and/or the SVN manual sections on this
topic.
--
Regards,
Jean-Marc
--
. ___
. @@ // \\ "De Chelonian Mobile"
. (_,\/ \_/ \ TortoiseSVN
. \ \_/_\_/> The coolest Interface to (Sub)Version Control
. /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2858561
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-18 21:20:37 CEST