Re: [cross-project-issues-dev] [emft-dev] May service releases explicite

[Oisin Hurley <oisin.hurley@xxxxxxxxx>]

Just butting in here because I have had so much fun and games
with this in the past :)

> Generally I think, you're not binary compatible if you narrow down your
> dependency ranges. You may provide better solutions than your workarounds,
> but you must not remove the workarounds if the better solutions depend on
> higher versions (of ProjectA).

That's it exactly - you extend your version range dependency so that you code
can pick up the 'fixed' version if it is available, but you should keep the
workaround in place so that your code still functions for those who have only
got the 'non-fixed' versions installed. Otherwise you break a subset of your
consumers. Yes, it can be messy this way - that's why it's a handy thing to
keep binary compatible and binary non-compatible branches developed in step
with each other (IMHO).

 --oh