Re: general subversion theory for developers?

Sean Moss-Pultz wrote:

> Do any of you guys use a method that you feel works particularly
> well? I would love some guidance.

Commit to trunk unless you've got a very good reason not to (like you're
working on major experimental functionality). Merges will always be
painful if you've left it more than a couple of days. Run an automated
build to build and test your code every time someone checks in -- that
way you know the trunk is always good, no matter how fast people commit
to it. You can use tools like CruiseControl or AntHill for Java,
CruiseControl.Net or Draco for .Net, and (if you're willing to be
experimental), DamageControl for more general CI.

References:

http://www.martinfowler.com/articles/continuousIntegration.html
http://cruisecontrol.sourceforge.net/
http://www.urbancode.com/projects/anthill/
http://ccnet.thoughtworks.com/
http://www.chive.com/products/draco/
http://damagecontrol.codehaus.org/builds/damagecontrol/docs/index.html

Cheers,
Mike.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 8 17:55:34 2004