cumbersome that it was worth. Currently we don't use source control, we
just have copies of the files on our client machines (which we use as our
development environments) and then once we test everything, we upload it to
the production server. I just don't personally see much of a use to keep
every little change you made in a document. I don't find it very often that
I have to roll back and application to a point where I can't just re-code it
in a few minutes. If it's a major change, then I definitely make backups
before applying the change.that's just me though. I guess it depends on
your personality.
John Burns
-----Original Message-----
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 9:59 AM
To: CF-Talk
Subject: RE: Source Control: everyone uses it, right?
we don't use it. formally. we have dev boxes, and production boxes.
1. develop
2. test
3. backup production code
4. upload new code
5. test new code
6. run with it or recover if not good
...tony
tony weeg
senior web applications architect
navtrak, inc.
www.navtrak.net
[EMAIL PROTECTED]
410.548.2337
-----Original Message-----
From: Daryl Walsh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 8:55 AM
To: CF-Talk
Subject: Source Control: everyone uses it, right?
Anyone not use source control? Would you hire a web development shop to work
on a project if they routinely did not use source control but relied on the
developers to maintain informal source control?
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
