Perforce vs Subversion
-
You should make Perforce tell you why you should pay money to use their product vs. the free subversion. Then wade through the fud and find the real differences and compare.
Todd Smith
-
You most definitely do not need an apache server to use subversion, not even for remote repository mirroring. We use windows servers and the included service utility that comes with Subversion.
Cum catapultae proscriptae erunt tum soli proscripti catapultas habebunt
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
A rule of thumb: if your team is 10 developers or less, just pick SVN. Otherwise, Perforce may be a way to go.
-
We just started using Subversion with Tortoise windows client after I was convinced by people here (probably in one of those threads you were linked to) and I'm very happy with it. The deal sealer for us was that now I can commit and have my changes saved here and in another country at our web server simultaneously for protection. It works fine, I've had no issues, other than lack of knowledge at first on how to do things, and was able to get up and running and using it within a few hours and that's coming from not having used any source control before of any kind. We use it for several pretty big projects, one has over 20,000 files in just under 7,000 different folders in it. The only way you can really truly compare two different software packages is to take the time to set them both up and try out a typical cycle from initial checkin to simulating a release and branching etc. Then you will know for certain with confidence and not just someone else's opinion.
Cum catapultae proscriptae erunt tum soli proscripti catapultas habebunt
Good to hear that you are still very happy with the decision to start using SVN.
Scott.
—In just two days, tomorrow will be yesterday. [Forum Guidelines] [Articles] [Blog]
-
Yeah, we did, happily. It was only when I discovered the ease of branching a current release while working on the next release and the automatic mirroring of my changes in our L.A. server that I saw any reason to change. Although I must admit that I've since found other things to like about it. :)
Cum catapultae proscriptae erunt tum soli proscripti catapultas habebunt
Good to hear! FWIW, I've found the subversion metadata properties to be very useful, both the inbuilt (e.g. svn:ignore, svn:keywords) and our own that we've added. If you use an issue/bug tracker, read the TortoiseSVN help on how they've implemented it. The other advice (as an svn user since v0.29) I'd give is add a pre-commit hook to fail if no log message was entered. I've adopted the svn developers message format:
* path/to/file (modified member): details of change (another member): details of change * path/to/another/file (some member): details of changeBring on v1.5 and merge tracking! -
SVN is the standard abbreviation. For windows users I'd recommend reading the TortoiseSVN docs for how to setup either the Apache mod or svnserve server.
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
I would look at Plastic SCM. Been using it for awhile as it has many features for a very good price.
-
I have not used SV so I can't say it's better or worse than Perforce. If SV works well and is easy to maintain, I would use it, why? Because its free... You have to have an Apache serv for SV server right? I've used P4 in conjunction with about 20 users a couple years ago. Of course Perforce is free up to two users and x-amount (forgot the count) of workstations per user. No support for free. Perforce documentation was more than adequate. I am demo-ing it now on a project that a co-worker and I are working on. I just installed it on my workstation...really easy. The MVS plug-in works great, auto-check out, yada yada. Create a Job in P4 and as you work on it, you can attach a changelist (revision set) to the Job. So when you look at a particular Job, you can see all the changes that were made to complete the Job. SV may do this too??? You should at least check P4 out, great diff/merge tools. P4 has a little interaction with command line interface, but that shouldn't scare you (if you would be), just for setting up groups/users and such. My 2¢.
-
I would look at Plastic SCM. Been using it for awhile as it has many features for a very good price.
Simon Murrell wrote:
Plastic SCM
never heard of that. I'll keep my eyes open. Have you used perforce or Subversion? how does plastic SCM stand against those two? I have used PVCS and VSS in the past,:| which I have no desire to go back to them.
/* I can C */ // or !C Yusuf
-
Simon Murrell wrote:
Plastic SCM
never heard of that. I'll keep my eyes open. Have you used perforce or Subversion? how does plastic SCM stand against those two? I have used PVCS and VSS in the past,:| which I have no desire to go back to them.
/* I can C */ // or !C Yusuf
In terms of pricing it is $100 cheaper on starting base users. I found it very easy to install and to get up and running with a 25mb install file. It has parallel development capabilities with branching, private workspaces for each developer as well as remote and distributed development. It also supports ACLs for each element in the system so the security is very powerful. Finally I run it off Windows and with Visual Studio 2005. However it can off Mac, Linux and Solaris. It also integrates with Eclipse, VB, Visual Studio, JDeveloper, TTS, Jira and Ontime from Axosoft. I have found it to be good for my use. However I would recommend testing it to see it fits your requirements.
-
SVN is the standard abbreviation. For windows users I'd recommend reading the TortoiseSVN docs for how to setup either the Apache mod or svnserve server.
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
We switched over to perforce from a homegrown solution 8 years ago and have never looked back. It met our requirements: 1. UNIX (HP, Sun, Digital, AIX) and Windows support. 2. Lightweight clients 3. Fast 4. Easily administrated We currently have 70 developers plus our internal web team using it with no issues. Admin is still only one person. Scalability - we have ~ 50,000 files in hundreds of branches, no issues. Bullet proof - AFAIK, we've only lost 3 days in the last 8 years due to the perforce server being down. We are a commercial company and paying for top quality CM tools is a no-brainer compared to the cost of not having them. If you are on a much smaller team with a tight budget then SVN might be the answer. I don't personally have any experience with it so I can't comment on capabilities.
-
We switched over to perforce from a homegrown solution 8 years ago and have never looked back. It met our requirements: 1. UNIX (HP, Sun, Digital, AIX) and Windows support. 2. Lightweight clients 3. Fast 4. Easily administrated We currently have 70 developers plus our internal web team using it with no issues. Admin is still only one person. Scalability - we have ~ 50,000 files in hundreds of branches, no issues. Bullet proof - AFAIK, we've only lost 3 days in the last 8 years due to the perforce server being down. We are a commercial company and paying for top quality CM tools is a no-brainer compared to the cost of not having them. If you are on a much smaller team with a tight budget then SVN might be the answer. I don't personally have any experience with it so I can't comment on capabilities.
tj_nd89 wrote:
We are a commercial company and paying for top quality CM tools is a no-brainer compared to the cost of not having them. If you are on a much smaller team with a tight budget then SVN might be the answer.
Right now we are only 2 developers. From the reading I have done on perforce's website, it is free up to 4 users. cost wise at the moment both are the same. I got very solid and compelling argument for both tools. time permitting I want to test-drive both and see which one works best for us.;) Thanks all for your inputs.
/* I can C */ // or !C Yusuf
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
I know this is thread should be limited to Subversion, but can I throw in my $0.02 and recommend CVS? Our shop has been using it for 7 years and it works great! Again it's open source and free like subversion. http://www.march-hare.com/cvsnt/[^]
-
May be this topic has been beaten to death several times.:~ If so, please pass the links to those discussions. We are looking to replace VSS with either one. Any pros and cons list comparison of both. I googled and found several comparisons. It appears most of the comparison are one sided.:rolleyes: Do you use one or both? what is your take on either one? Thanks for your thoughts.
/* I can C */ // and !C Yusuf
I would try out Git.. It's pretty nice and really fast.. minus the small learning curve. After a few days of reading docs.. you'll master it. Git was developed my Mr. Linus Torvald to be a replacement for CVS and SVN. There is actually a google video about Git which he presented. Documentation is kind of hard to find. I did manage to find a really good website by a computer science student/students that will help you with understand Git and how to use it. http://www-cs-students.stanford.edu/~blynn/gitmagic/ Good luck on your search. -BJ
Keep Coding
-
I know this is thread should be limited to Subversion, but can I throw in my $0.02 and recommend CVS? Our shop has been using it for 7 years and it works great! Again it's open source and free like subversion. http://www.march-hare.com/cvsnt/[^]
-
excuse my ignorance.:confused: Doesn't SVN picks where CVS left off. It is a faint recollection, I thought the reason of SVN development is to fill some of the shortcoming of CVS. Did I chew it wrong?:~
/* I can C */ // or !C Yusuf
No worries Yusuf. There are pros and cons to both CVS and Subervsion. In the end, it's personal preference. Here's a link to a quick comparison that may shed some light on your decision. http://www.pushok.com/soft_svn_vscvs.php[^]
-
Yeah, we did, happily. It was only when I discovered the ease of branching a current release while working on the next release and the automatic mirroring of my changes in our L.A. server that I saw any reason to change. Although I must admit that I've since found other things to like about it. :)
Cum catapultae proscriptae erunt tum soli proscripti catapultas habebunt
-
Good to hear! FWIW, I've found the subversion metadata properties to be very useful, both the inbuilt (e.g. svn:ignore, svn:keywords) and our own that we've added. If you use an issue/bug tracker, read the TortoiseSVN help on how they've implemented it. The other advice (as an svn user since v0.29) I'd give is add a pre-commit hook to fail if no log message was entered. I've adopted the svn developers message format:
* path/to/file (modified member): details of change (another member): details of change * path/to/another/file (some member): details of changeBring on v1.5 and merge tracking!