I don't get it, surly this is just the use of branches? You make a branch for change A, work on it a little and then have to switch to something else. No problem, create branch B and do some work on that for a while. Nothing new there.
I completely agree with Noah. There's absolutely nothing new there. Anyone doing concurrent developments on a project does this (I hope). That's what branches and merging are for, and SVN is great at it. The fact that MS gave that concept a fancy name is quite funny though.
As someone who doesn't do a lot of development with branches I found the article extended my understanding of what you can use them for, but I'll agree that this isn't a new concept - just new to me.
Sign in with 
OpenID
Shelving was a big part of the pitch for MS's "Team System" when I saw them present it last year.
Shelving and apologising for the price.
I don't get it, surly this is just the use of branches? You make a branch for change A, work on it a little and then have to switch to something else. No problem, create branch B and do some work on that for a while. Nothing new there.
Noah Slater - 9th January 2007 17:45 - #
I completely agree with Noah. There's absolutely nothing new there.
Anyone doing concurrent developments on a project does this (I hope). That's what branches and merging are for, and SVN is great at it.
The fact that MS gave that concept a fancy name is quite funny though.
Cyril Doussin - 9th January 2007 23:34 - #
As someone who doesn't do a lot of development with branches I found the article extended my understanding of what you can use them for, but I'll agree that this isn't a new concept - just new to me.