version control - Are Branches In TFS's Default Collection Root Problematic? -


been using tfs think while. got new job & i'm wondering if use of tfs wrong. used seeing team projects listed in default collection root. however, work, seeing branches @ root (as well).

i haven't said yet, means (further) branch given (branch) folder root of default collection. seems big issue me...but maybe not.

so questions are...

  • is having branches @ default collection root wrong?
  • is legitimate practice?
  • what problems can cause?
  • should something?
  • how possible create branches at-root? (i tried test , couldn't)

enter image description here

i speculate branches @ root created in 1 of 2 ways.

  1. they created using "branch team project" in create team project dialog.
  2. the folders / projects created separately , baseless merge performed between folders creating branching relationship.

as if it's idea or not. no. can't think of upsides this. downsides here small list.

  1. it's untidy, not best reason cause confusion if have many branches, example if use feature branching.
  2. if team using work items track work cause problems. work items exist inside team project , cannot moved between them. current thinking using tfs have single team project of code , use "teams" , "team rooms" organise work. way tasks can moved between teams without need create duplicate tickets.

if it's aesthetic issue it's not worth changing @ point, might want suggest future projects / branches don't follow pattern.

it's subjective, you're new team i'd bide time see if there practical issues being caused this. if there suggest approach changed. if not i'd live it. work team have same issue, , whilst don't it, on day day basis doesn't make difference having more conventional branch / folder structure.

if decide challenge it, make sure have plan migrate better!


Comments

Popular posts from this blog

how to insert data php javascript mysql with multiple array session 2 -

multithreading - Exception in Application constructor -

windows - CertCreateCertificateContext returns CRYPT_E_ASN1_BADTAG / 8009310b -