I'm in charge of switching our 10+ years old code base from SVN to Git. Currently we have one single monolithic repository containing all of our projects. We have shared libraries and multiple projects using said librairies.
I've been looking for a way to host all of our projects into seperate repositories. I have looked at both submodules or subtrees for the solution, but I do not know which one to choose as of now. One of our core librairies is our database framework (old and homemade) which always needs to be up to date in every project that uses it as all our applications work with a single-central database.
As of now, the releases are all manually executed by the repo administrator. The goal is, ultimately, to setup our TFS server to have CI and speed up the deployment process of our applications. Here is an exemple of what would be the (I think) best scenario. But first, just a short list of what the project depencies look like:
WebProject-A uses FrameworkLibrary-B
WebProject-C uses FrameworkLibrary-B
WindowsService-D uses FrameworkLibrary-B
I'm working on adding new features to WebProject-A. Thoses features require some new changes to the data model, maybe a new table or a new column. That means I need to make changes to FrameworkLibrary-B. Now, WebProject-C and WindowsService-D are too, linked with FrameworkLibrary-B. What that means is, on a check-in for FrameworkLibrary-B, I need to build A,B,C and D and deploy A,C and D. On a check-in for project A, I need to build A and B and deploy A.
Many of our developpers have little experience with Source control (svn update, svn commit). The goal would be to have something powerful for subproject management and yet, something that wont scare the developpers away from Git. Do you have any recommendation as to what would be the best solution for Git repository management in this instance.