4 ms·
If both projects share a source control system, you can commit a change and update its downstream usages all at once, with no breakage even temporarily. However
by skybrian 12y ago
If both projects share a source control system, you can commit a change and update its downstream usages all at once, with no breakage even temporarily. However, this requires source control that scales company-wide. (Git doesn't qualify.)
- RickHull 12y agoYeah, git-repo-per-project was an unspoken assumption. Also, "upstream and downstream" may not suffice analytically, as many interdependencies in this model do not satisfy DAG, even if they ~should~. Agile projects aren't often built so much as grown.
- jaggederest 12y agoI think the problem you're assuming here is that dependencies are automatically updated to use the latest version. That sounds like pretty strong coupling in a way that means other problems are lurking somewhere. Team A should be able to develop without having to consult Team B constantly. That means you have to be mature about deprecating things before you just remove them, but I think that's what the whole article is about.
- skybrian 12y agoYes, there are all the usual ways of deprecating things, migrating the callers, and then finally removing the deprecated methods. This is rather tedious and people tend not to do it for small cleanups like renames. If you can do it in one commit, you can work faster and hopefully get cleaner code. Of course even if you have atomic source control commits, you don't have atomic deployment so there's still migration to take care of, but it works fine for in-process API's.
- Raphael 12y agoOf course, Facebook is supposedly one 50GB repo.
- jaggederest 12y agoNot sure why you're bashing on Git here, it certainly does scale to and handle this use case pretty effectively. This is precisely the problem that submodules solve, much maligned though they are. It's essentially a dependency problem, and we have good answers for those. Edit: Also I am fairly certain that the kernal experiences these kinds of issues, and is the flagship user of Git.
- skybrian 12y agoThe Linux kernel is tiny compared to a large company's need for source control. It easily fits on one machine. Think about what you'd need to put all the projects in an entire Linux distro in one source control system; that's more like the scale I'm talking about. Linus built a tool that suits his needs well but he's not working at the same scale.