This project has moved. For the latest updates, please go here.

How to Transition from Basic to Standard to Advance

Feb 25, 2011 at 4:53 PM

We're trying to setup a standard for how to do branching and find the guidance very helpful.

Some of our exiting projects clearly need the Advanced or maybe even the Mature branch plans, but most are relatively simple and can get by with Basic or Standard.  When we start a new project we're not usually sure if we're going to need all of the Advanced stuff so we'd like to setup the project with the Basic plan to start and only grow it into Standard or Advanced if we really need to.

The guidance document (page 5) says:

The elements of these plans are additive; starting with the Basic plan will allow you to transition to the Standard plan if your product or branching requirements become more complex.

How do you do that?

If I've been using the Basic plan for a while, but find I need to do a ServicePack how do I "transition" to the Standard plan?  Do I rename my Release branch to ServicePack and then create a new Release Branch from it?  Most of my experiences with renaming a branch have been bad -- things tend to break.  Or do I need to do some branch reparenting, magic?  Or do I declare the current Release branch as historical releases mark it read only and create the ServicePack branch from the last changeset that went into the old release branch and then create the new Release branch from it?

If this is covered in the docs please feel free to respond RTFM, but please point out the doc and page I should be looking at -- I haven't found it yet.

thanks
Perry

 

Developer
Feb 25, 2011 at 5:41 PM

Perry,

My recommendation would be to follow your last option: "declare the current Release branch as historical releases mark it read only and create the ServicePack branch from the last changeset that went into the old release branch and then create the new Release branch from it"

Like you have seen nothing but problems arise from renaming. Periodically I get cases referred to me from Premier support where things don't seem to be working correctly (merging issues, upgrade issues from 2008 to 2010, and so on). Almost everyone of these cases has a *hidden* rename issue. Or the user deleted a file and added a different one with the same name. I don't *think* you will have a problem if you follow option one and rename Release to Service Pack and branch a new Release from it (just don't use exactly the same name as the old banch :), maybe use RTM instead) . So I suppose you will be ok following that course of action. Most of the rename issues I have seen have been on the development side. I think 2010 handles these situations better so I wouldn't be overly concerned. Renaming in and of itself might not be bad. But renaming and then reusing the old name might be something to avoid.

Regards,
Bill Heys
VS ALM Ranger

Developer
Feb 25, 2011 at 5:50 PM

Or alternatively for the current release, leave the name of the Release branch as is and branch a new RTM branch from it. Then *treat* the Release branch as a Service Pack branch. Then starting with the next release go back to a more intuitve naming (Service Pack, Release).

Regards,
Bill Heys