![]() |
Version Control Recommendations need
I am looking for some sort of source management solution for this year. In the past we have just stored everything on an FTP server which worked but was rather annoying. I am considering something like CVS or Subversion. Im am looking for pointers as to the pros and cons of each.
|
Re: Version Control Recommendations need
If you plan on doing heavy amounts of tagging and branching, use CVS. Otherwise, I recomend Subversion.
In my expieriance, Subversion tools are much better than CVS ones (translation: TortoiseSVN is much more streamlined and strange than TortoiseCVS). It is also easier to setup a server on Windows and Linux. (In Subversion, use the included mini-server or add mod_svn to Apache. In CVS, use a Linux box. CVSNT is the only Windows CVS server and I have not heard good things about it.) Subversion also handles directories, removals, and renames infinately better than CVS. CVS cannot handle directories; removals are so-so; renames consist of either moving the file in the repo (so that the entire history is moved, and no reference to the old name exists), or delete the old and create a new (so that there is no connection between them. As for the tag/branch comment, here's the thing: in SVN, you have to actually create a new repository for each tag and branch, in addition to the trunk (main line of code). CVS handles tags and branches natively. For further details, I defer to google. (BTW, I've found that Subversion has much better "official" documentation than CVS.) |
Re: Version Control Recommendations need
How can I set up a Subversion server? Can I run it on my team's website?
|
Re: Version Control Recommendations need
Quote:
|
Re: Version Control Recommendations need
Quote:
If you are unable to setup a Subversion repository on your team's website, then I've heard that CVSDude will offer free Subversion or CVS repositories to nonprofit organizations, but you do have to write an email to them explaining how your team is educational, etc. Anyway, good luck. |
Re: Version Control Recommendations need
Quote:
|
Re: Version Control Recommendations need
Quote:
|
Re: Version Control Recommendations need
You also can try SourceAnywhere Hosted.
It's a SQL-based source control tool delivered as a SaaS application,you can connect to the SourceAnywhere Hosted server from anywhere, anytime. There is also a Standalone Edition. Thanks, Catherine Sea |
Re: Version Control Recommendations need
Our team uses SVN right now. We have used CVS as well in the past, but we migrated over last season. So far SVN has been much nicer. TortoiseSVN is great, ViewVC is nice if your host supports it (or if you're running your own server), and even the CLI tools are nicer.
As for running the server, our team's web host (Dreamhost) fully supports SVN repositories and ViewVC on the server (there are even tools in the site control panel for it), but I know that many do not. If you can't run it on a web server, it shouldn't be too hard to run it on somebody's computer at home (that's what we did with CVS for two years). |
Re: Version Control Recommendations need
I would look at this thread:
http://www.chiefdelphi.com/forums/sh...threadid=59801 However, just to note, subversion runs best on linux based servers with (apache?).. At least that's what team 694 has. It is a great way to allow multiple people to access the code from anywhere. As the poster previous to be said, Dreamhost will set one up for you through their control panel. If you don't have them you want to test it out, or don't know how to set it up on your server, my favorite free hosted solution is google code. Though they give you a paltry 100MB of repository, text doesn't take up that much space. It's free and secure (yay google servers) so it really is a great option. code.google.com |
Re: Version Control Recommendations need
Quote:
|
Re: Version Control Recommendations need
We're currently using SVN, it seems to work fairly well, just annoying to reset up once your files get all mixed around. Losing your master folder makes things confusing >.<
|
Re: Version Control Recommendations need
I've used CVS for many many years, so that's what we use for our team's code. At work, we've just switched from CVS to SVN (subversion), so far I like it. We may switch to SVN for the team's code, but we may wait until post-season to do that.
|
| All times are GMT -5. The time now is 04:31. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi