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

Re: Directory Structure

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Thu, 10 Jul 2008 22:37:22 +0100

2008/7/10 Navaneeth K N <navaneethkn_at_gmail.com>:
> Hello All,
> I am new to "Subversion" and seeking your help on setting up a repository
> directory structure. I am planning for starting an open source project
> hosted in the "Google code".
> I read the documentation and understood the recommended layout like
> "/trunk","/branches" and "/tags". Usually which directory will be used to
> commit changes ? I believe it is "trunk".

Correct, that's the most common way of working.

> If so which is the directory users
> used to download the code ?

What do you mean by 'download'? Checkout the code to work on it, or
download the dinished application to run it?

> If it is also "trunk", and developers has
> committed partial code, user downloading next time will get partial code,
> right ? So is there any way to use developers working directory as a
> separate one and when everything looks fine, the release files will be
> copied to "trunk" directory.

You should control which versions you release. Normally the compiled
code is placed on a separate download page, not in the repository, so
release files are stable.

Read the subversion book to get a better overview of what subversion
is all about.


: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-10 23:37:30 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.