View Full Version : Revision Control for project: details?
GBGames
07-10-2004, 09:12 PM
I'm just starting to get into my first commericial project. I have never used revision control before, and I am learning how to use subversion.
My question is: What do you usually keep in your repositories (whether you use CVS/BitKeeper/Arch/etc)?
I know source code and data files like audio, images, and scripts would go there, but do you also keep documentation? Design docs? Basically, is your entire project and its related files kept in revision control, or do you usually keep the design document outside of it in its own directory/server somewhere?
Thanks!
Jim Buck
07-10-2004, 10:44 PM
Source code, all docs related to the game, including contracts and design docs.. and also artwork.
ggambett
07-10-2004, 11:04 PM
We use CVS, although Subversion may be worth a try (it's essentially CVS compatible but with additional stuff such as rename, directory move, and so on)
We have everything there, including docs.
serg3d
07-11-2004, 02:05 AM
Using CVS, keep source, docs, and part of artwork. Thinking about moving to Subversion.
wazoo
07-11-2004, 06:14 AM
You're probably getting the picture from the previous posts, but it's a grand idea to put EVERYTHING and anything project related into version control..
I'm currently running the cvsnt service piece on my server and have just about everything in there...project code, design docs, website, etc..
My only problem is that bugzilla seems incredibly unfriendly to the win32 platform..so for now I'm just tracking bugs/changes to the project with a spreadsheet...(also in cvs of course).
If you decide to go the CVS route, I heartily recommend checking out TortoiseCVS. It's a CVS client that plugs itself right into windows explorer. VERY handy and smooth..
hth
Rainer Deyke
07-11-2004, 09:53 AM
I just want to say that subversion rocks. I recently switched from CVS to subversion, and the latter is so much more pleasant than the former that I cringe every time I have to touch one of my old projects which are still in CVS.
Oh, and I also keep everything in the repository. Code, art, design docs, and web site.
GBGames
07-11-2004, 10:36 AM
I want to thank everyone for the info.
As for CVS, I tried to learn it awhile back, but I had no project to work. It's difficult to learn something when you don't use it.
At my univeristy's Linux User Group, we had Brian Fitzpatrick, one of the developers of Subversion, give a talk. It was very informative and amusing (he's a funny guy). As for CVS being stable, Brian mentioned that the codebase for it is just horribly hacked together. If you want to update it or fix it, it WILL crash. Subversion was made to replace CVS, and for the most part it works just like it "except when there was a compelling reason not to."
So I decided to forget about CVS and I've started using Subversion. So far I've messed around with it, and now I am pretty confident in how to use it for some tasks, although I did come up with some problems that show I am not very familiar with how to use it still. The SVN book didn't cover some details though, such as personal choices like where most developers will keep their repositories (I had to ask in the IRC channel for that). And naturally project specifics like what to keep in the repository aren't covered (that's what this thread is for).
Thanks again! B-)
Justiciar
07-11-2004, 06:38 PM
I keep everything in our CM repository -- code, project metadata (number of defects, time per phase, defects per phase, etc.), business plans, design docs. Everything related to my business I keep there.
I use Perforce as a CM tool. I like it alot, but the terminology for tasks can be a bit confusing at times...
Anthony
Mark Fassett
07-11-2004, 07:35 PM
Keep everything. And then back it up on a regular basis.
I use Perforce. It's much better than just about anything else I've used - CVS, VSS, Subversion (although - with subversion, I gave up during the install). It's also cross platform.
jaggu
07-17-2004, 01:47 AM
I also use Perforce. They offer a fully functional 2 user version which is really useful for us indies. Grab it off http://www.perforce.com/
I tried a lot of revision control systems b4 settling on perforce. Never regretted it. Had untold horrors with CVS and its front-ends. Perforce is also very fast.
Grimreaper
07-17-2004, 04:21 AM
Perforce simply rocks - the tool is great, their cross-platform support is great (i use it on BSD, linux and windows just fine), easy to use, best source/asset management app out there. IIRC, even MS licensed Perforce's code for their own use.
grimreaper