> I disagree. > I'd much rather people checked in a local chuck of finished work (like, > say, a > new Flex client wigit), irrespective of having finished the server half of > the feature. > The build being broken will be picked up,
Yup - the breakage will be picked up, and will waste someone elses time while they figure out what is causing the breakage, whose responsibility is to fix it, etc. I simply can't imagine working in an environment where it's considered OK for my work to be interrupted by another developer committing broken code simply to avoid having a proper backup strategy. and I'd much rather have changes on > the thing we back up rather than scattered across developers machines. Back up the developers machines then. It also encourages developers to go a long time between commits, which > increases the chance of a conflict. If the changes are substantial enough that a dev may go more than a day or two without commitng, then use a branch - THAT's what they are for. > Version control is not meant as a backup system, > > Again, I don't see the harm in using it as one. I do. > future. If I need to pull a particular revision, I should be able to look > > at the history and see, via clear commit comments, what changes were > made > > to create that revision, and be fairly confident that if I actually > check > > out that revision that it will function. > > That's what tags and branches are for. > Revisions mean nothing, esp. in SVN. Version != Revision. A version is a concrete snapshot of your repository, via a tag or branch, that has a semantic meaning. A revision is basically a way to reference a particular state of the repository in the history - it's hardly meaningless. You can MAKE the revisions meaningless by not having any discipline around commits. You never know if any of your revisions actually work, since you encourage broken code to be checked in, so you are relying only on the versions you choose to create via a branch or tag if you need to roll any code back to a previous state. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:277788 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
