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

Re: Repository construction

From: Anthony Ettinger <anthony_at_chovy.com>
Date: Fri, 7 Mar 2008 08:49:36 -0800

On Fri, Mar 7, 2008 at 8:21 AM, wimpunk <wimpunk+gmane_at_gmail.com> wrote:
> Hi,
> A college has a rather strange idea on setting up his repository and I'm
> wondering if it will cause any troubles for subversion since I'm the
> administrator.
> He's used working with SourceSafe and now he's planning to use a
> directory structure looking like this:
> project/major/module/minor/version
> Personally I would remove major, minor and version from the structure
> but he really wants it that way. When he starts a new major, he creates
> the substructure again and copies the latest version to this major.
> As far as I understand, there's no server-side objection doing this.
> For subversion is doesn't matters where you create your branch. Is this
> correct?
> Will it differ at the server size concerning the size of the db if we
> use a more normal construction like this:
> project/module/{trunk,branches,tags}
> I hope there's no problem doing his idea since it already took some time
> to convince him using subversion.
> Kind regards,
> wimpunk.

 ./trunk should always be the latest, and when he's ready to release a
version bump, he can just create a new tag from ./trunk.

1/1/08 - Cut release 1.0
tag trunk as 1.0 (results in ./tags/1.0)

2/1/08 - Cut release 1.1
tag trunk as 1.1 (results in ./tags/1.1)

etc. etc

You can find out more about tagging from svnbook.org

Anthony Ettinger
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-07 17:50:07 CET

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

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