Category: Features & Releases
July 09, 2013by Bill Baffy, Software Engineer (@p4bill)
July 03, 2013by Gabe Weiss, Technical Lead for P4V
Task branches, available in 2013.2 P4V, alleviate a lot of the mental stress around deciding when to branch for a fix or feature, and when to do the work directly in the active branch. With task branches, branching is nice and cheap.
June 18, 2013by Mark Warren, European Marketing Director, @mark_warren
“Living is easy with eyes closed.” – John Lennon
Many Perforce users have homegrown or ad hoc reporting and dashboard tools built around Perforce server logs and tools like P4toDB. But what if you need a quick overview of the state of a project, codeline, or team?
June 13, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
June 06, 2013by Randy DeFauw
Ever had your Perforce repository become unresponsive because someone ran a script that was hammering the repository in a while(1) loop? The Perforce server process (p4d) is normally a very gracious host, accepting any and all requests from users and automated processes. However, there are some cases where you'd like it to be a little more choosy. Otherwise, a poorly constructed script, malicious activity, or just plain old too much traffic can overwhelm p4d for a period of time.
June 03, 2013by Randy DeFauw
The 2013.1 release of Perforce now supports IPv6 addresses. That means that you can run your Perforce services on an IPv6 address, and use IPv6 addresses in the Perforce protections table. Host names that resolve to IPv6 addresses are also supported.