How to label branch for a new release

Question

0.00/5 (No votes)

See more:

TFS

What is the best way to label code for a new deployment? Maybe it is better to create an new branch instead?

Posted 10-May-13 17:42pm

Walterls

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Answer 1 · 2013-05-10T17:52:00

Solution 1

Probably the best resource I've found so far on using TFS and best practices:

http://tfsguide.codeplex.com[^]

[EDIT]

This is the one that I meant:

http://vsarbranchingguide.codeplex.com/[^]

The one above is an older book for TFS 2008 I think.

Posted 10-May-13 17:52pm

Ron Beyer

Updated 10-May-13 18:04pm

v2

Ordun · Answer 2 · 2013-05-11T18:33:00

There is no standard for doing this. You can organize your code as you want. Personally I like to create a branch for major and minor versions. If you plan to rebuild older versions, adding labels makes this even easier.

I’d suggest something like this but again, there are many ways to do this

$\Branches
    \1.1
    \1.2 (branched from 1.1)
    \2.1 (branched from 1.2)
    \2.2 (branched from 2.1)