If you use Subversion as a part of a well thought out development
strategy, it is miraculous, time-saving, butt-saving, etc. If you
don’t have a reason to use it, and a plan to use it consistently,
then it’s a waste of time to set it up.
I use it, like it, it has saved my butt numerous times. And there are
times that I don’t use it. I try to be aware of the break-even point
in terms of the hour or so it takes to set up, and the additional
time it adds to making changes.
Also realize that putting a Freeway file in subversion amounts to
making a zip of it every time you save. That’s all it’s good for. You
can’t put a freeway file in subversion, make some changes, have
someone else make some conflicting changes, and do anything except
choose who wins.
Where it’s really magical is in the hand-coded stuff I do a lot of.
There, you can make some changes to a function, I make can some
incompatible changes to the same function and ten other things, and
we can reconcile the changes at a very granular level at check-in.
I highly recommend Pragmatic Version Control with Subversion, from
The Pragmatic Programmers. http://pragprog.com
Walter
On Feb 13, 2008, at 4:53 PM, Todd wrote:
Comments, opinions or experience regarding the use of Subversion for
team - or possibly standalone - development? Are there better
alternatives available? I may have to use it (or something similar)
for a possible gig and I would appreciate insight from anyone who has
used it for production work. The closest thing to a collaborative
tool that I have is SubEthaEdit that’s built into Coda which is not
the same thing.
Todd
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options