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

SVN Process

From: Neson Maxmelbin (RBEI/EMT5) <Maxmelbin.Neson_at_in.bosch.com>
Date: Tue, 16 Nov 2010 17:52:22 +0800

Hello .

I want to setup a reliable development process for SVN in our environment.

Here is what I am planning to propose for the process.

Each project in the repository will have the following folders -

The initial baseline of the project will be in trunk folder.

For the first Release, the trunk is checked out , changes made and then commited into trunk.
It should then be tagged into the tags folder as Release_xyx .
The tag Release_xyz is then considered as baseline for the next Release.

For the next Release, developers should checkout from the tag Release_xyz .
Make the necessary code changes.
Switch to trunk
Commit changes to trunk
After all changes are done, Integrator tags the HEAD revision to a new tag Release_xyz2


My questions -
* Does this sound like a common procedure followed by SVN users and is it reliable?
* Do you foresee any issues with this process
* How can I prevent people from commiting into tags
* Can I lock a tag?
* While tagging I get options for "Create copy in Repository from" 1> Head revision from Repository , 2> Specific revision from repository 3> Working copy . I always choose the first option. Is it correct?
* With regards to the tags, does the SVN repository maintain a full copy or only a delta copy ?

I appreciate your valuable suggestions. Thanks

Thanks and Regards
Maxmelbin Neson
Received on 2010-11-16 10:54:14 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.