On Thu, Aug 21, 2008 at 4:54 PM, Peter Dimov <pdimov@pdimov.com> wrote:
Robert Ramey:
Peter Dimov wrote:
Robert Ramey:
Legitimate dependencies do exist. A may depend on a bugfix changeset of B, > or a new feature changeset of B.
As I said- that would be a bug. In fact this would be an old bug.
If merging B into the release branch breaks library A -
_Not_ merging B into release before A is merged may also break the newly merged A.
Well, A was already working, then it has already been addressed with some workaround or something like that.
A is working on the release branch against B. A+dA is working on trunk against B+dB. But dA can't be merged into release since it depends on dB.
This isn't a big deal in practice since the author of A will simply ask the author of B to merge first.
Isn't it also possible that in the interim, B+dB now also depends on A+dA? i.e. neither can merge without breaking the other - they must both be merged at once, or merged in steps to prevent breakage. --Michael Fawcett