3 ms·
> The outcome of multiple repos should be modular libraries. Yes; also they should all be treated as separate, independent products. Where multi-repos go wrong
by Cthulhu_ 8y ago
> The outcome of multiple repos should be modular libraries.
Yes; also they should all be treated as separate, independent products. Where multi-repos go wrong is when a whole product spans multiple repos, and a feature of the product depends on features being added or altered in multiple projects.
Ideally, the split should be so that nobody has to work across multiple repos to finish a feature.
The github / NPM ecosystem is IMO a good way to look at it; libraries that are all independent of one another who have a (usually pretty good) adherence to semver.
- amelius 8y ago> Ideally, the split should be so that nobody has to work across multiple repos to finish a feature. That does not sound realistic. Often I have to add a new function, and I think: where (in what library) does this function belong, and very often it's not the main library I'm working in at that moment.
- lmm 8y agoAdding a new function anywhere other than the leaf project where it's used is premature. Organize around user-facing functionality. Pull out common libraries as and when you have something common enough to factor out (and, crucially, test independently), not before.
- jacques_chester 8y agoSo the answer to needing to open multiple PRs is to open multiple PRs.
- lmm 8y agoThe answer is to adapt your working patterns so that you never have multiple PRs on the critical path. Long-term codebase quality may require multiple PRs, but delivering user-facing functionality doesn't.
- amelius 8y agoAnd what if I wanted to add a method to a class? Or a method and a data member?
- pjmlp 8y agoYou get the library owner team to do it and bind to the new released version. Microservices without network headaches.
- pjmlp 8y agoUsually libraries are owned by separate teams.