Please send us the Architecture of PVCS, features, complete guide and merits & demerits.
Thank youudayasri.maddineni[at]gmail.com" class="mycode_email
Posts: 14,118
Threads: 61
Joined: Oct 2014
PVCS Version Manager (originally called Polytron Version Control System) is a software package from Serena Software Inc., for version control of source files. PVCS follows the "locking" approach to concurrency control; It has no built-in join operator (but has, however, a separate join command). However PVCS can also be configured to support multiple users simultaneously trying to edit the file; In this case the second chronological switch will have a branch created for him / her so that both modifications, instead of conflicting ones, will appear as parallel histories for the same file. This is unlike Concurrent Versions System (CVS) and Subversion where the second committer needs to first merge changes through the update command and then resolve conflicts (when they exist) before actually committing.
Originally developed by Don Kinzer and published by Polytron in 1985, through a history of acquisitions and mergers, the product was sometimes owned by Sage Software of Rockville (1989), Maryland (not related to Sage Software UK), Intersolv 1992, Micro Focus International 1998 and Merant PLC 2001. The latter was acquired by Serena Software in 2004, which was later acquired by Silver Lake Partners in 2006. Synergex carried both the PVCS Version Manager and the PVCS Configuration Builder (an extended utility, including A variant of the command line tool do) to various Unix and OpenVMS platforms. In 2009, Serena Software clarified that it will continue to invest in PVCS and provide support to PVCS customers in the foreseeable future.
The version of PVCS Version Manager 8.5 (2014) presents a new functionality and a new platform of support. In the year 2016, Micro Focus International announced the acquisition of Serena Software to become the custodians of PVCS.