"Thorsten Ottosen" <thorsten.ottosen@dezide.com> wrote in message news:4463A34E.1060400@dezide.com...
Beman Dawes wrote:
Thorsten Ottosen wrote:
Also, what happens if several libraries depend on your library in trunk, but can't work with the dependency found in stable?
You have to wait for the other libraries to be merged to stable.
I think I need to explain this better:
I upgrade library A in trunk s.t. it is no longer compatible with library B (which depends on A) in either trunk nor table.
Since A don't work with B.stable, I can't commit A to stable. Since B.trunk can be made to work with A, B.trunk can be made to work. However, as soon as one tries to commit B.trunk to stable, it can't because it won't work with A.stable.
Basically we need to commit A and B at the same time. Neither can go alone.
Does it make sense?
Yes. The upgrade to A is a breaking change that affects other libraries. So even though the new version of A works well and is itself stable, it should not be merged to STABLE until all other libraries that depend on it are stable. Then all of the libraries involved should be merged into STABLE at the same time. I've updated the doc to make that clearer. Thanks, --Beman