Alan Coopersmith writes: > > Note that, at least for the minor release binding typically used in > > Solaris, it doesn't matter. All that other distributions need to do > > is pick a point in time, start a branch, and they're good to go. > > Everything that went in up to that point is already known to have a > > proper release binding, and it doesn't have to match when Sun pulled a > > branch. > > Except that ARC's have allowed teams to change interfaces incompatibly > when they haven't actually had a binding release yet, so we'd have to > at least know when people fork their minor branches to know when it's > safe to allow that exception, unless we totally clamp down and say once > it's in any build it's set for the life of that release train.
Indeed. I suspect we need to be able to say that no branches occur between those points (distributions reporting back to c-teams?), or simply declare that such midstream changes are now prohibited. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
