News for hackers. Stuff that matters.
Re:Keeping master green at scale by ljm on Thursday April 18, 2019 @04:22PM (#19694451)
This is essentially the problem go has had, precisely because you could only ever pull the latest from master.

Introduce a breaking change into a common library and now you have to update every other dependency to support it.

Not so bad in a monorepo. But when your codebases are distributed?

Re:Keeping master green at scale by jeletonskelly on Friday April 19, 2019 @09:04AM (#19699220)
It's almost like semantic versioning exists for some reason