if ( ! blogClogged )

TFS VC Branch/Merge and Streams

As a response to Eric Lee's post about TFS VC and Streams I started this as a comment to his blog entry then decided it was too long and would thus make it my own entry with a pingback.

I recently did a demonstration with a potential client that was moving from VSS and evaluating which VC product they would move to. They were doing branch-by-task in VSS (a brave proposition in my book). I represented to them how they would similarly work using TFS and in a similar method as Eric discusses.

I also showed how they might decide to use more of a mainline development or feature crew development. I personally don't see a ton of difference in feature crew and branch-by-task- perhaps granularity, perhaps not. Can anyone else explain to me how they differ?

Like Eric I tend to keep up with CM Crossroads and now the PnP  contribution to guidance on CodePlex on branching. I do think compelling points exist in stream based models. In the end I see streams as wrappers and workflow around the same branch merge process but those are very valuable things to have.

I think I will look around for a workflow and security model that wraps around TFS VC and if I don't find one... well I'll just create one as an exercise in feasibility.

What do you think?????