3 ms·
How big of a team and how big of a codebase? Often massive amounts of commits during development wreak havoc on interconnected projects. At least in Git, not so
by silverbax88 12y ago
How big of a team and how big of a codebase? Often massive amounts of commits during development wreak havoc on interconnected projects. At least in Git, not so much in TFS. Mercurial kind of splits the gap.
- Nursie 12y agoI've worked with git in small teams (~5) and with other systems like clearcase in larger teams (20+, ~100 if you count sister teams). So long as everyone is working on their own branches and pushing/pulling to a shared stream when features are complete, and that pushed to a release stream when releases are to be prepared.... I don't see why folks couldn't comm8t every 5 minutes if they wanted. It's more interesting to discuss the strategy for moving code from personal branches to development, and dev to release.
- JoeAltmaier 12y agoEven more complicated: moving code from branch to branch. To share needed support, or bug fixes, or test interoperability. If you can push to the shared stream and the others pull it up to their branch, cool. But with interoperability testing of incomplete features that's not ok.