Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [emft-dev] May service releases explicitely require other service releases?

 Am 25.09.2010 11:53, schrieb Sebastian Zarnekow:
Hi Eike,

sorry, my initial mail seemed to be confusing.
No problem ;-)


Assuming ProjectA 1.0 had some issues that lead to the fact that ProjectB 1.0 had to implement some workarounds and disable some other features. Those issues were solved in A 1.0.1 hence the workarounds are no longer necessary and the previously disabled features are no longer necessary in B 1.0.1 if - and only if - A 1.0.1 is present. How would one describe these if not by means of concrete deps to ProjectA 1.0.1?
I still don't understand the "diasable features" part.

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).

Cheers
/Eike



Back to the top