Is this a valid LGPL scenario?

Question

Suppose I have Project X under closed source. It references/links to component Y which is LGPL, we make modifications to component Y

1) We release Project X binaries with the source to the modified component Y

OR

2) We contribute component Y modifications back upstream (to the original author(s)) and release Project X binaries without component Y source.

Does any of these scenarios comply with the LGPL?

Answer 1

Option (1) is certainly OK. Option (2) is probably not, because there is no real way of "contributing modifications upstream".

Answer 2

I would say that both are fine, but I'm no lawyer, and you know what that means.

LGPL does not place restrictions on your code, but you cannot make proprietary changes to the LGPL:d code, but you're not suggesting you do that, which is why I'd say both are fine.

Answer 3

1) is fine.

2) is not: you have to distribute y source (or at least a written offer to do so). Your users would have a hard time looking for your modification in depths of upstream patch repository (a bug tracker, whatever).