John Plocher wrote:
Richard Lowe wrote:
It cannot be up to consolidations individually, how would you then
handle cross-consolidation dependencies?
Very carefully :-)
If the dependency is on public interfaces that have a Committed
stability, then this isn't much of a problem. The consuming
consolidation can use any Minor or Micro release from the set
of available releases that have the feature in question.
If the dependency is less stable, then the consuming consolidation
needs to do more work validating and testing.
If the dependency is one of the contracted Private ones, there is
little to no wiggle room - both consolidations *must* release in
lockstep. This is why depending on implementation details is bad,
and why the ARCs push teams to develop public Committed interfaces
instead.
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.
-- Rich
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
