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

Branching, versioning misc questions

From: Fabio Miranda Hamburger <fabmirha_at_ns.isi.ulatina.ac.cr>
Date: 2005-06-07 19:54:08 CEST


We have implemented SVN in our web development team. We have a directory
called /usr/respositories which has a directory for each project. We did
smthg like:

$svnadmin create /usr/repository/project-foo
$svnadmin create /usr/repository/project-bar
$svn import /apache/foo/public_html file:///usr/repository/project-foo
$svn import /apache/bar/public_html file:///usr/repository/project-bar

I have the following questions reagrding this situation:

1. Is a good practise to have a repository for each project if they dont
share files ?

2. Does this model make sense? Now, each developer has to 'checkout' a
project in their hgome directory, make changes, and then 'commit', but,
what if he remove a function that another developer, doing somthg similar,
actually need it ? If the project manager is the only person able to
'commit' changes how to manage the web developer changes that some of them
are accept but other dont.

3. Regarding project manager role, how to implement a hierarchy of users?
Or, better, are the changes handle by revision, so, if the developer A
commit bad code, and B commit good code, then, I take revision from B and
how to avoid A commited code?

Sorry for the confusion, too many concepts at the begining,

Thanks in advance,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 7 20:24:45 2005

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.