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

Re: reposity versioning

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 03 Dec 2008 10:34:07 -0600

Giulio T wrote:
>
>> We wouldn't be keeping the same reposity, for every new project i create a
>> new repository. I think the checking out from core and then importing to
>> the new repository is what will do the trick.
>
> I dind't say checking out from core. I said copying, meaning copying with the OS command (not svn cp command).
>
>> I agree about the revision numbers. I think they are more concerned about
>> "version" numbers. They always want the new project to start at version
>> 1.0, if that has any bearing. That being said, i'm not a developer so I'm
>> still trying to get a handle on the whole process and they aren't the best
>> at describing what they want. I think this will work fine for what I need
>> though.
>
> If they actually meant "version 1.0" rather than "revision", maybe it would simpler to keep everything in one repository and use the tags instead. You create a new project copying (this time with svn) the core, then create the usual structure of branches and tags and then, I you really want, you create the first tag, called 1.0. Something like the following
>
> svn mkdir <URL to new project> -m"Creating new project blah blah"
> svn copy <URL to core> <URL to new project>/trunk -m"Copying core"
> svn mkdir <URL to new projct>/branches -m"Creating branches"
> svn mkdir <URL to new project>/tags -m"Creating tags"
> svn copy <URL to new project>/trunk <URL to new project>/tags/1.0 -m"Tagging version 1.0)

If you are new to subversion concepts, you might want to browse the book
to understand how trunk/branches/tags are typically used. You might
really want a 'release branch' policy where at certain points like a
major version release number you copy to a branch for final
testing/development to isolate it from larger changes that might be
happening in the trunk. In that scenario you might incorporate the
product release/version number in the branch name. This doesn't have
anything to do with repository revision numbers.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=978957
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-03 17:35:13 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.