Incremental deployment is a good idea if you can fully automate it (e.g. robocopy or MSI as discussed). I've been on a project where we used to do this manually - each release we had to locate files that changed ourselves. Needless to say it wasn't pretty :)
> (Our developers check in and out > at will...right now there is no constraint on when a file should be checked > in except that checkins at the end of the day should build). This sentence worries me. Your main/release branches should 1) always be in a working, buildable state 2) be checked in when it's finished, not at the end of the day. I wrote a post about this last year: http://richarddingwall.name/2008/11/23/back-to-basics-good-source-control-check-in-habits/ Rich -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
