I have been asked to migrate a legacy version control TFS2008 to TFS 2015 using GIT. As newbie to GIT, I need to Understand/create a strategy on how to migrate these source control. My TFS2008 has around 150 (some related and many unrelated) applications.
My current structure is as show below. Out of 150 apps every quarter there would be release for at least 15-20 apps and I need to create a new branch for that. In TFS 2008 I was able to organize the same under a DEV branch and once the project is complete , it gets merged to the prod branch. This was simple way of doing things with VSS, TFS in Microsoft world.
I learned that better way to use GIT is to different repository for different application but that scenario is ruled out. I tried to understand concept of Orphan branch and sub-modules but they look complex. I need guidance on how these types of structure can be migrated to GIT
Prod
-- Applicaiton 1
-- Applicaiton 2
-- Application 3
..
..
..
-- Applicaiton 149
-- Applicaiton 150
Dev
-- Applicaiton 1 Branch - Project Release 1
-- Applicaiton 1 Branch- Project Release 2
-- Some Big Project Affecting multiple Apps
-- Applicaiton 1 Branch for BIG Project
-- Applicaiton 26 Branch for BIG Project
-- Applicaiton 45 Branch - Project Year 2014
Any help in migration strategy to treat each application individually would be helpful to me.
If my question has caused confusion. Please do ask for clarifications
Finally, I went with approach of having one repository for each application.