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

Re: 'good practices' in php programming with subversion

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-02-24 14:10:46 CET

On 2/24/06, brunoml <bruno2.boudinski@worldonline.fr> wrote:
> Hi,
> I would like to know what are 'good practices' in php programming :
> - working copy on programmer's computers, copy (with a batch, a macro in IDE) to
> "test/debug" web server and commit
> - working copy on "test/debug" web server (so, several programmers on the same
> WC) and commit.
> - other...

If everyone works from the same working copy, then aren't you losing a
lot of the collaborative ability SVN gives you? Your chances of
trampling over each others' code go up significantly IMO. Plus you
all have to remember to specify --username on each commit (or
otherwise require a login for each update/commit), else you can't
reliably identify who made what changes.

My preference (and what we do with our Java web app):
Each dev has his own working copy
Each dev has, on his desktop, a unit testing environment
The central dev server is used for integration testing of all changes.
 Code only gets to this server via svn checkout, developers cannot
copy files to it directly.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 24 14:13:13 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.