October 10, 2013by Sam Stafford, Developer at Perforce Software
In the days before streams, it was commonly accepted that if files had different names in different branches, you would need to set up a branch spec that mapped one set of file names to the other if you wanted to integrate changes between those branches. When we began developing streams functionality, we knew we would need to provide another way to handle refactoring within streams, since the branch view used to merge changes between a stream and its parent is dynamically generated and is supposed to be a relatively simple function of the paths specified for each stream – hence we came up with a system for matching different filename variants within a source and target to each other and setting up resolves between them.
October 08, 2013by Bryan Pendleton, Software Engineer
Image: Sewing Daisies w/Flickr
Perforce replica servers can be configured in a variety of ways. To learn more about replica servers, run 'p4 help replication' and look through the documentation for replica servers, or consult the System Administrator's Guide.
One of the important decisions that you must make when configuring a replica server involves how it will handle its archive of versioned file contents.Posted In:
October 04, 2013by Sven Erik Knop, Technical Marketing Engineer
The Global Enterprise
Software development has become a global enterprise with development teams spread around the world. I recently read an interesting article on the challenges posed to software architects and team leads to ensure the success of such an undertaking. The article asserted that the benefit of spreading development around the world is a less costly, but more responsive and nimble workforce that takes advantage of local resources and skills. The greatest challenge, it continued, is communication between different teams, especially the visibility of the contributions of each group.
October 02, 2013by Perforce
Here at Perforce, we’ve been talking about versioning everything for a long time, but what does the industry say on the topic? Thanks to relentless pitching that some say borders on stalking from our marketing team, the Editor-in-Chief of Dr.Dobb’s took a look at what it takes to version everything using SCM.Posted In:
October 01, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
I'm presenting a webinar for developers on "hacking Perforce" and it got me thinking about how the best version control tool for your development environment is the one you build yourself.
Whether you go with a commercial or open source system, no version control system can perfectly match up with your development pipeline's needs. Fortunately for those of us who like to build version control systems for a living, making a highly scalable, secure, and resilient version control system isn't a cakewalk.
September 30, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)