• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Software Management: PVCS or SVN

bshole

bshole

Diamond Member
We have used PVCS for about 15 years for software version management. We are considering a migration to SVN.

Has anybody here used both PVCS and SVN? Is SVN vastly superior to PVCS? Why? Would it be difficult to migrate 15 years of software archives from PVCS to SVN?
 
I have used both, but only as a developer (in java development) and never as someone tasked with setting either up. PVCS seems to have some difficult installation and set up (at my previous, there was literally one person who could install and set it up in an organization of a around 1000 people). The experience wasn't bad using it, however, there was no integration with any other tools we used.

SVN, on the other hand, at my current employer is integrated with our bug tracking software as well as our IDE. However, we use eclipse so I doubt there isn't a PVCS plugin.

The difference from what I have seen, is SVN facilitates and ease of merge from local to server based source. Multiple people can change files and simply merge at check in. PVCS, from what I've used of it at least, doesn't have that feature. SVN also is integrated with our bug / tracking system and will associate every change you check in with the current issue you are checking in for. I wouldn't say SVN, from my experience, is that much vastly superior than PVCS, but I am not very picky as long as the tool works.

Merging all your versions and branches from PVCS to SVN, I cannot comment on at all. This is something I have never done.
 
I have yet to find a proprietary version control system that works better than open source alternatives. SVN is far easier to use and more flexible than PVCS, StarTeam, Harvest or any of the other bloated, expensive alternatives out there.
 
Never even heard of PVCS before this thread. Apparently it is local-only? Wow, that is some ancient stuff there! Heck, I even consider SVN to be pretty dated compared to distributed source control like Git or Hg.

I guess it depends on what your needs are. I couldn't imagine using local-only source control.
 
There is a program called tailor that can migrate between various source control systems. It can normally maintain the grand majority of the history and only occasionally gets confused when something is very strange.

But I wouldn't move to SVN today, the world has moved onto Git. SVN is certainly better than CVS that it replaced but its far from a good source control tool, and you will find Git does a much better job of dealing with branches and merges and renames.

Try tailor, you should just be able to run it and have it migrate and you can then look through what it did and how much success it had with the conversion.
 
I prefer a central repository, so I'm an SVN fan myself. Git seems to be more popular these days.
 
Leros said:
I prefer a central repository, so I'm an SVN fan myself. Git seems to be more popular these days.
Click to expand...

You can have a central repo with Git, Hg, etc. It just isn't required to have one. But you still can. You commit to local repo and push to the central repo.
 
Apparently our IT department will not allow us to install ANY open source software, so we will not be using SVN or GIT.

Serena PVCS

http://www.serena.com/index.php/en/products/pvcs-vm/

Serena PVCS Version Manager (PVCS VM)

Thousands of software developers around the world rely on Serena PVCS Version Manager (PVCS VM) for their version control needs. PVCS Version Manager is one of the most reliable, trusted, and proven solutions on the market.
Simple and fast out-of-the-box install. Stable execution

With Serena PVCS VM, you don't have to worry about your technology stack changes. We ship you the most reliable and stable version control solution with all required components in the box. Whether you use Linux, Windows, or another operating system to develop software, Serena PVCS VM can help manage your versions regardless of platform.
IDE integrations. Out of the box

With Serena PVCS VM, you don't have to search the Internet for integrated development environment (IDE) integrations for the most common development environment. Serena includes them in the box.
Security. At all times

Serena PVCS VM is known for its strong security layer, including single sign-on (SSO) and Common Access Card (CAC) support.
Built-in file server

Serena PVCS VM has a built-in file server that supports fast implementation and lower maintenance and allows the splitting of metadata from file revisions.
Configuration control

Serena PVCS VM provides baselines to retain a snapshot of development effort at a point in time, as well as branching to develop alternate versions of development artifacts.
Click to expand...
 
Some companies just don't realise its 2013 and no body buys software anymore. A lot of the best tools are open source ones. But at least now you know, your IT team is full of morons. That is always good to know.
 
BrightCandle said:
Some companies just don't realise its 2013 and no body buys software anymore. A lot of the best tools are open source ones. But at least now you know, your IT team is full of morons. That is always good to know.
Click to expand...

Agreed. Your IT team is obviously full of more "management"-type people than "technical"-type ones. And Software Development is not an industry where you want to be a decade behind the curve in terms of what is current. If software development is your company's primary deliverable, then they won't be revisiting this issue in another 15 years because they will have gone belly-up by then.
 
douglasb said:
Agreed. Your IT team is obviously full of more "management"-type people than "technical"-type ones. And Software Development is not an industry where you want to be a decade behind the curve in terms of what is current. If software development is your company's primary deliverable, then they won't be revisiting this issue in another 15 years because they will have gone belly-up by then.
Click to expand...

Yeah, this is probably the same sort of IT department that forces everyone to use IE8 because it is "safer" than Firefox or Chrome... Sucks the OP has a retarded IT.

If I were to choose today, I would go with GIT. The closed source VCSes all pretty much suck.
 
If IT support is obstructing the operations of departments that actually create something, and won't budge, then it's up to the management to hammer the stupid out of them. If the management isn't capable of doing this even when informed, then the company has much deeper problems than bad IT. Have you made a serious attempt of taking this high enough upstairs, bshole?

I think PlasticSCM looks best among non-open source solutions, and among the very few that are actually comparing themselves to git and hg. Haven't used it though.
 
Sometimes its IT that pushes stupid policies like this, but sometimes its left to IT to enforce a stupid policy set by a companies legal department.

Dave
 
I'll also throw in my vote for git or hg. SVN is dying quick, and it couldn't come any sooner IMO.

Jump over your IT and go to management. Tell them that they're costing the company more money by forcing you to use proprietary, costly software than a tried, tested, secure solution. There's plenty of people and organizations who use git without any security issues (aside from those you create yourself).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top