News for hackers. Stuff that matters.

A comment on Monorepo or Multirepo? Role-Based Repositories. Parent comment

Re:Monorepo or Multirepo? Role-Based Repositories by chrisseaton on Saturday October 12, 2019 @01:34PM (#21234786)
I think they do, but there is only ever one single version in use - the version in the repo.
[ Parent | on HN ]
Re:Monorepo or Multirepo? Role-Based Repositories by minxomat on Saturday October 12, 2019 @02:28PM (#21235158)
Yes, and that prevents duplication of work when it's time to upgrade: https://github.com/microsoft/TypeScript/issues/33272
[ Parent | on HN ]
Re:Monorepo or Multirepo? Role-Based Repositories by user5994461 on Saturday October 12, 2019 @05:49PM (#21236606)
If so, they would have a massive problem upgrading libraries like numpy because there are too many and too big breaking changes between releases.
[ Parent | on HN ]
Re:Monorepo or Multirepo? Role-Based Repositories by jumpingmice on Saturday October 12, 2019 @06:44PM (#21236885)
Inside Google's main repo there are different build targets for libraries with incompatible API changes that are too difficult to fix all at once, e.g. there might be numpy_1_8 and numpy_1_10 separately.

Python at Google muddled along for years without numpy at all so it's not like anyone would be seriously harmed by having an old release in the repo.

[ Parent | on HN ]