undefined | Better HN

0 pointsmvc3y ago0 comments

> What does the team do? Do they wait until every team who depends on them is ready to work on updating? Do they try to work out how the depending team is using their code so they can update it themselves?

versioned multi-repos may solve this for the team[s] demanding incompatible changes to shared code but any team who was happy to use the shared code as it currently is, and was expecting to also benefit from any upcoming compatible improvements will see only problems with this "solution".

Better to give the new incompatible behavior a new name. Deprecate the old name. Then callers of the old thing can fix on their own schedule.

0 comments

cortesoft3y ago

> versioned multi-repos may solve this for the team[s] demanding incompatible changes to shared code but any team who was happy to use the shared code as it currently is, and was expecting to also benefit from any upcoming compatible improvements will see only problems with this "solution"

Normally this is solved with semantic versioning... you pin to a minor version, so you get all non-breaking changes, but don't pull in breaking changes.

mvcOP3y ago

In my experience semantic versioning is more aspirational than something you can actually rely on.

Many times bug fixes are not back-ported to prior lines of dev

Other times, claims of backward compatibility on minor version releases are wrong.

j / k navigate · click thread line to collapse