Version Control
by Jason Bertles · in Technical Issues · 09/26/2001 (5:42 pm) · 9 replies
How have people been approaching version control in their scripts? We've only just started looking at the scripting side of the Torque engine and already we can see a great need for some sort of control processes, particularly with two of us working on the engine simultaneously.
We haven't looked to see whether Source Safe would work with scripts (I guess there's no reason why it shouldn't), but is this over the top? Is there something else out there that people use?
Please fill me in on what you all do.
-Jason
We haven't looked to see whether Source Safe would work with scripts (I guess there's no reason why it shouldn't), but is this over the top? Is there something else out there that people use?
Please fill me in on what you all do.
-Jason
#2
09/27/2001 (11:51 am)
rick which ones should we download.... verion 2 or 3 and both sourceand binaries right? 
#3
Can someone give me a quick rundown on how to use CVS? Or a link to a quick tutorial? I had always thought it was used over the web and ignored it pretty much. Now it seems like you can use it on your own machine as well?
I'm assuming you check files out of a central repository and then check them back in with changes? Or something?
I've always used manual source control and it's never worked that well, especially if more than 1 person is coding :(
09/27/2001 (1:47 pm)
Ok, I'm an idiot :)Can someone give me a quick rundown on how to use CVS? Or a link to a quick tutorial? I had always thought it was used over the web and ignored it pretty much. Now it seems like you can use it on your own machine as well?
I'm assuming you check files out of a central repository and then check them back in with changes? Or something?
I've always used manual source control and it's never worked that well, especially if more than 1 person is coding :(
#4
A few Tutorials I found searching on google.com:
Link
Link
--Rick
09/28/2001 (8:39 am)
Download Win32 Binary WinCVS 1.2A few Tutorials I found searching on google.com:
Link
Link
--Rick
#5
CVS Book
Far easier to understand for the layman (and some good meat for those of us who've been using CVS a while) than most of the other tutorials out there.
I ended up buying the book to support him ... he's released most of his 'treeware' book under the GPL.
09/28/2001 (9:30 am)
Best online resource I've found:CVS Book
Far easier to understand for the layman (and some good meat for those of us who've been using CVS a while) than most of the other tutorials out there.
I ended up buying the book to support him ... he's released most of his 'treeware' book under the GPL.
#8
--Rick
10/06/2001 (7:50 am)
I just installed the CVS server at our ISP (thursday). Tim and I have been doing some configuration and resolving a few last minute issues. After it has been running smoothly for a couple days we'll open it to the Troque Developers.--Rick
#9
we've been using CVS at the office for a while now in a Linux/Mac environment, so heres my 2p:
* I've used the Cederqvist manual and its served me well,
http://ftp.cvshome.org/cvs-1.11.1/cvs-1.11.1p1.pdf
* always remember: the server is the original and has priority. If it shouts at you and doesn't want to commit your changes its probably got a good reason
* if you want to move files while preserving history, commit your changes, throw away your local copy, log onto the server (ssh/telnet), shuffle stuff around and do a complete checkout on your local system again.
* don't forget to inform co-workers of drastic changes :)
* a version control will most likely force you to reorganize the way you work and the way you communicate with your co-workers. Don't underestimate the additional coordination involved, but also the benefits gained!
* you'll probably need an additional information repository to keep your team informed about branches etc. A team-website might be right. The CVS-modules file is NOT sufficient! Bring the additional communication channels to live along with your CVS server!
have fun,
Tony
10/08/2001 (7:15 pm)
hi,we've been using CVS at the office for a while now in a Linux/Mac environment, so heres my 2p:
* I've used the Cederqvist manual and its served me well,
http://ftp.cvshome.org/cvs-1.11.1/cvs-1.11.1p1.pdf
* always remember: the server is the original and has priority. If it shouts at you and doesn't want to commit your changes its probably got a good reason
* if you want to move files while preserving history, commit your changes, throw away your local copy, log onto the server (ssh/telnet), shuffle stuff around and do a complete checkout on your local system again.
* don't forget to inform co-workers of drastic changes :)
* a version control will most likely force you to reorganize the way you work and the way you communicate with your co-workers. Don't underestimate the additional coordination involved, but also the benefits gained!
* you'll probably need an additional information repository to keep your team informed about branches etc. A team-website might be right. The CVS-modules file is NOT sufficient! Bring the additional communication channels to live along with your CVS server!
have fun,
Tony
Torque Owner Rick Overman
Soon, we will be opening up CVS server access to the Torque Engine, so you can pull down the latest code anytime rather than waiting for us to build a patch file to download. So it might just be a good idea to download CVS and get used to it.
Try downloading WinCVS here.
--Rick