Perforce Software today announced several key advances to its software version management system. This release of Perforce includes new capabilities for advanced distributed version control that keep developers productive even when they are disconnected from Perforce’s shared versioning service. In addition, new replication technology improves system performance and scalability for remote teams.
Jim Duggan, Research Vice President of Application Strategy at Gartner, said, “Combinations of distributed versioning with classic file-based versioning schemes allow new and better accommodations of the needs of the developer for flexibility and the larger needs of the organization for control, traceability, accountability and security.”
P4Sandbox Delivers Independence, Flexibility and Performance With Perforce Sandbox (P4Sandbox), developers can work on private copies of their projects while staying informed of project status on the shared versioning service. They can quickly create private local branches, including task or feature branches, and can also access the system’s built-in workflow, Perforce Streams. P4Sandbox manages communication with the shared versioning service and can merge changes in either direction when users require. Another benefit is the improved system performance that comes from offloading work from the shared service.
Olga Zaigralina, Principal Software Engineer with EMC, said, “We evaluated Perforce against two distributed open source systems. And P4Sandbox with its local versioning and branching capabilities supported our decision to choose Perforce. P4Sandbox looks like a big win for developers who want more flexibility while working with a shared software version management system.”
In related news, Perforce also announced today that it has extended the options for free access to its software version management product (see “Perforce Offers Software Version Management System Free for up to 20 Users with New 20/20 Program”).
How P4Sandbox Works
P4Sandbox uses a local repository to create a remote branch from the shared Perforce versioning service. Users can work with their local repository and access all of Perforce’s versioning features, even if the connection to the shared service is slow or non-existent. Developers only need to be connected to the shared versioning service when they are exchanging data.