How to handle branching when you plan to rewrite in the future?

My development team will soon switch to branching - we were cursed by SourceSafe, and we are moving to Team Foundation Server - and I'm interested in something.

Traditionally, when we make major changes to our product, to such an extent that even the folder structure or file names remain unchanged, we create a new root folder in the original control.

for example

$/V1.0
$/V1.1
$/V1.5
$/V2.0

etc.

I am brand new to branching, and one of the things I read is that you can use different branches for different versions of your product. Now, when you talk about fixing or a small change or modification of the code, where in the worst case you can add new files - it makes sense.

"V-Next" , (not , , , ), , , , , , -, ? ($/V2.0 ) ?

+3
6

Subversion. 3 :

V * . , , , .

. , , . , "V-Next" , , trunk.

+4

TFS, "" .

VCS , .

, ( ), , , , , .

, , .

V2.0 :

  • .
  • 2.0

, :
V2.0_Refactoring, , .

+1

. ( ) "" , , .

0

, , - "" , , . , , , .

/ , , . , , .

, " " . , , . , TFS // .., , .

0

, :

V-next. , , .

(1 ), . , , .

. , , .

SCM.

0

Source: https://habr.com/ru/post/1702584/


All Articles