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

RE: subversion based code development/management model

From: Lieven Govaerts <lgo_at_mobsol.be>
Date: 2006-08-20 15:31:42 CEST

This is somewhat how we manage the repositories for our teams. I explained
our setup some time ago on the users list, you can find an archived copy
here: http://svn.haxx.se/users/archive-2005-12/0887.shtml.

What are the specific problems you have to set things up?



> -----Original Message-----
> From: Stephen Adler [mailto:adler@stephenadler.com]
> Sent: zaterdag 19 augustus 2006 20:46
> To: users@subversion.tigris.org
> Subject: subversion based code development/management model
> Guys,
> I want to setup the following code development/management
> model. To do so, I want to use subversion with the
> appropriate access controls.
> The repository layout
> Trunk/
> Tags/
> Branches/
> To create a new project, the following must be done.
> 1) Create a template directory layout under Trunk/
> -- Done by repository administrator
> 2) Make a branch of the inital layout into the Branches
> directory. Give Developer (group of developers)
> read/write access to the branch.
> -- Copy of initial layout into Branch done by repository
> administrator
> -- Developers have full read/write access to the Branch
> to code and develop.
> 3) When coders reach the stage of having a release candidate,
> they tell the repository administrator to
> make a release.
> 3.1) Repository administrator merges the branch into the trunk.
> -- this can only be done by the administrator
> 4) Release Candidate is made, a copy from trunk to tags is made
> -- this is only done by the release administrator. The
> tagged release has only read access.
> The idea being that there is a repository administrator who
> has full access to the repository.
> The developers only have read/write access to one designated
> branch. A release is made by the developers telling the
> repository administrator to merge the branch into the trunk
> and then make a copy of that into the Tags area.
> Developers cannot create new top level branches. Developers
> cannot merge into the trunk or make their own releases.
> My subversion repository is setup with https access. (i.e.
> I've added the appropriate modules to apache 2.0 daemon.)
> I've also setup authenticated access to the repository, but
> its only at the top level of the repository (i.e. at the
> Trunk/, Tags/ Branches/ level) So right now, if you have an
> account on my system, you can do anything to any part of the
> repository. Basically its wide open and there are no access controls.
> Any help and/or comments are greatly appreciated.
> Cheers. Steve.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 20 15:34:25 2006

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.