Category: Features & Releases
January 10, 2014by Perforce
In many ways 2013 was our best year ever. For starters, we spent more time with our customers to better understand their needs and, in return, got valuable feedback across our product portfolio. On the product side, it was certainly our busiest year. Not only did we launch several new products in 2013, we also made many significant improvements to our core versioning engine and clients.
Let’s start by looking at the products we unveiled last year.
December 03, 2013by Amy Ichnowski, Engineer at Perforce
As of the 13.2 product release, a new P4 Connection toolbar is available in P4VS. This handy feature displays your current connection information within the IDE environment, including the server, port, user, workspace, and stream (if applicable). It allows you to switch between your 5 most recent connections, create new ones, and disconnect from the Perforce server.Posted In:
November 12, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
I think 'p4 edit' is by far the most cursed Perforce command on Twitter. Folks coming from Subversion and Git are accustomed to an implicit checkout workflow, and being forced to ask the version control system for permission to change something is grating. Conveniently, Perforce supports implicit checkout as well! Let's take a look.
November 06, 2013by Nathan Fiedler, Software Engineer
Git Fusion’s goal is to give Git and Perforce users an uncompromised experience using the version control tool of their choice while still being able to work together seamlessly. The 2013.2 release gets us closer to that goal and, at the same time, makes Git Fusion easier to administrate and use.
Introducing Support for Git Tags
Prior to this release, any tags that were pushed to the Git Fusion service would only be preserved as long as the Git Fusion repository was intact. Now tags of commits are preserved in the Perforce depot, which allows them to be rebuilt if the need arises, as in the case of repopulating the Git Fusion repository. The commit tags can be either annotated or lightweight; both are preserved equally well.
October 30, 2013by Murtaza Amiji, Director of Product Management
Distributed teams face unique challenges when they practice Continuous Delivery. For example, it’s critical to keep remote teams up-to-date with the latest code changes within an expected response time—past-due changes can cost the team valuable time and money. Similarly, new features require continuous integration via build and test automation, so that developers can receive immediate feedback, and can rapidly, reliably, and repeatedly launch new features. Network latency and bandwidth, and version management server capacity also become critical bottlenecks for Agile distributed teams, severely impeding Continuous Delivery. These challenges slow down the mainline, the team, and ultimately, the business.Posted In:
October 28, 2013by Bryan Pendleton, Software Engineer