September 30, 2011

Rolling in the Deep with P4V Streams Beta


Ready, Set, Re-Associate Your Workspace for the P4V Streams Beta!

Back in early June at the Perforce Users Conference, Gabe and I presented and debuted the long awaited Streams in P4V. The presentation rocked and the buzz and enthusiasm for Streams was better than any of us imagined. One of the highlights of the demo was a simple drag and drop of the workspace icon in the new Stream Graph from one stream to another stream. We dubbed this cool slight of the hand “Re-associating a workspace.” While some of us were riding high and strutting around with our big smiles, the customers were clamoring to get a copy for a test drive. Now the Beta is out! The Streams Dream Team pulled off a herculean effort to deliver high impact functionality that our customers can really dig.

What is re-associating a workspace?

Streams was initially designed with the idea that a user would have a workspace for each stream. The tradeoff for having a workspace per stream is that the workspaces are now a no-brainer to create. Perforce takes care of generating those complex client and branch views. You know, those icky funky and cryptic rules that determines how files move back and forth between the server and the local disk as well as between codelines on the server.

That’s cool. Who wouldn’t want that?

Well, on paper it sounds great, but we’re pretty saavy around here (well at least support is) so we’ve learned over the years that managing multiple workspaces comes at a cost for many of our customers. Especially those customers that have lots of codelines that share the same files, codelines that have huge binaries, or customers with slooow connections. That’s where re-associating a workspace comes into play. The user can now seamlessly use a single workspace in P4V to work in any of their streams. Yep, that means only managing one workspace no matter which stream the developer chooses to sling their code. Now check this out. If a developer uses the re-associate feature with the new smart sync, they can really get their groove on. The process of switching between streams can be screaming fast since the server limits the sync to only the minimum files that have changed between the streams. Who’s gonna tell me that’s not a sweet win for our customers?