Richard Lowe wrote:
And if ConsolidationA chooses to release, and it depends on ConsolidationB
which doesn't, ConsolidationA doesn't have any kind of stabilization
period for something parts of it depend on.
What am I missing here?
I presume "B" releases B1 with a new feature that "A" wishes to use .
This implies that the previous B0 release doesn't have this behavior,
and the new B1 will. The release timeline looks like
B0 released
... B1 development on the new feature happens
... B1 stabilizes their code base
B1 is released with the new feature
...
... time passes
...
A0(which depends on B1) is developed and released
All that [time passes] time is available for "A" to come to grips with
"B"'s new feature.
Oh! Do you mean to say that "A" would like to use something in "B" that has not
yet been released? This implies a timeline like:
B0 released
... B1 development on the new feature happens
...
... A0 developers discover this new feature and start to use it
...
A0 desires to release their new version, but can't because B1
hasn't been released
All this says is that the decisions, timing and consequences of choosing to
depend on a new feature from "B" rest solely upon the people developing "A".
If they want to use it, they need to wait for it to be ready.
-John
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
