Re: Thoughts on choosing a source code control system?
Re: Thoughts on choosing a source code control system?
- Subject: Re: Thoughts on choosing a source code control system?
- From: Zak Burke <email@hidden>
- Date: Mon, 13 Mar 2006 11:11:33 -0500
Jerry W. Walker wrote on 3/13/06 10:05 AM:
For any commercial project, I feel exposed
without a couple things in place: a good SCM system that supports
concurrent development among team members
I think Mike and Jerry have summarized the, "Is it worth it to even
bother with SCS?" issues very well. If managing your SCS is too much
work, it's because you are not managing it effectively. You don't have
to write a treatise for a one-line change to a three-file project, and
even a commit with no comments will save your butt when you need to roll
back to a previous release. A SCS makes this dead-easy.
And on a tangent from this theme, my experience is that if you stash
your SCS repository on a server with a regular backup routine already in
place, your code is much more likely to get backed up than if you just
keep it on your development box. Individually, it may not be hard to
rewrite a three-line shell script. But you'll be in a world of hurt when
your disk dies and you have to rebuild 100 three-line scripts from scratch.
and a solid, web based issue tracking system.
Two projects I've found to be very useful on this front are CVSTrac for
CVS (http://www.cvstrac.org/) and Edgewall Software's Trac
(http://www.edgewall.com/trac/) for Subversion. Both are free and
Web-based. Features include repository browsing, Wikis and
ticket-tracking systems that are tied to repository commits.
zak.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden