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

RE: Is SVN ready for use?

From: John Barstow <John_Barstow_at_gfsg.co.nz>
Date: 2002-12-09 23:14:37 CET

> What I don't know is how to enforse programmers to update and commit
> their changes on a regular basis. I asked already about "watch" and
> because it yet to come I wanna know how people work. Now my team is
> working with VSS and a version builder detects whether someone forgot to
> check-in files just before building. Unfortunately it happens pretty
> frequently. How to prevent forgetting?

We have the following in place:

1) A scheduled task or logon script does an 'svn update' every morning.
This ensures that the developers are always working on the most recent

2) An automated build routine that builds and tests the checked-in code
every day. If the developers are not checking in their code, they will keep
getting bug reports. If you need a stick, the system can mail the
build/test results to a manager every so often.

This can help establish the discipline. Once the developers get into the
habit, it's not really an issue. I check-in my own code multiple times a

John C Barstow

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 9 23:09:02 2002

This is an archived mail posted to the Subversion Dev mailing list.