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?
Hi Eike,

sorry, my initial mail seemed to be confusing.

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?

- Sebastian

On 25.09.2010, at 11:37, Eike Stepper wrote:

Hi Sebastian,

Comments below...

Am 25.09.2010 10:35, schrieb Sebastian Zarnekow:
Even if binary compatible I don't quite understand why one service release may not depend on another.
I generally assume that service releases make nothing worse, but sometimes they do in certain aspects. Hence I would like to have a free choice over what bundles I update and what other bundles not.

Assuming a project had some workarounds
What do you mean exactly?

or had to disable certain features
That's not allowed in a service release.

due to bugs in required projects: If these bugs were fixed in the SR, why shouldn't the dependencies be explicit about this?
Because it constrains my freedom to choose ;-)

You can't know if I have valid reasons not to update the dependencies.

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top