Perforce is a software configuration management system that is fast, robust, runs on over 50 platforms, and scales to over 3000 users on a single repository. It supports atomic submits and works well over wide area networks, including the Internet.
|Tags||Software Development Version Control|
Release Notes: In Perforce Server (P4D), the "p4 move" command was added to move and rename files in client workspaces, and the "p4 logtail" command gives administrators remote access to server log files. In the Perforce Visual Client (P4V) and Perforce Visual Merge Tools (P4Merge), depots can be managed in the Admin Tool, and HTML, audio, and video files can be previewed. Diffed files can be edited in P4Merge. The appearance of Perforce Visual Client (P4V) can be configured. A Java-native API for accessing Perforce was added. A plug-in was added for Eclipse and WebSphere Studio (P4WSAD).
Release Notes: The following components have been changed or introduced between the 2006.2 and the 2008.2 releases: Perforce Server (P4D), Perforce Visual Client and Perforce Visual Merge Tool (P4V, P4Merge), Perforce SCC Plug-in (P4SCC), Perforce Plug-in for Windows Explorer (P4EXP), Perforce Web Client (P4Web), Plug-in for Graphical Tools (P4GT), Perforce Defect Tracking Gateway (P4DTG), Perforce Reporting system (P4Report), Perforce Ruby, Perl & Python APIs (P4Ruby, P4Perl, P4Python).
Release Notes: Client workspaces have a new "SubmitOptions" field that allows users to specify how unchanged files should be handled on submit. "p4 submit" can also now detect files opened for branch/integrate that have been modified in the workspace. Submits can be up to 40% faster thanks to improvements in the database locking and buffering of the journal file. Several changes have been made to improve the management of remote depots, including better lock support and MaxScanRows/MaxResults support. The new MaxLockTime group property allows admins to limit the duration of locks held by members of the group.
Release Notes: The Perforce server can now log individual file access to an audit logfile. When this is enabled, the server logs every time file content is transfered to a client. The "p4 integrate" command was rewritten, leading to better performance, better recognition of previous integrations (resulting in fewer merges), and better base selection (resulting in simpler merges). The merge algorithm was also rewritten and produces fewer conflicts to resolve, making automatic merging ("p4 resolve -am") more likely to succeed.
Release Notes: The Perforce server can now log individual file access to an audit logfile: when enabled the server logs every time file content is transfered to a client. The 'p4 integrate' command was rewritten, leading to better performance, better recognition of previous integrations resulting in fewer merges, and better base selection resulting in simpler merges. The merge algorithm was also rewritten and produces fewer conflicts to resolve, making automatic merging ('p4 resolve -am') more likely to succeed.