Manish Chakravarty wrote:
Just one doubt though.
Say SUN introduces some package X into the ON core. Or say into JDS /SFW
*after* June 15th 2005.
Do those code changes make it back into OpenSolaris ?
Most of those changes went into the trees visible as OpenSolaris
first and came from there into Solaris. For consolidations
like ON & SFW, there is only one tree for Nevada now - the one
you see on opensolaris.org, from which Sun builds the SXCE/SXDE
binaries. (JDS is a special case, since they keep two trees for
Nevada, but both are on opensolaris.org - one is the "stable"
branch used for SXCE/SXDE builds, the other is the development
branches where they pull in new upstream releases and test/debug
until they're ready to push to stable. Builds of the development
branch are available for download from the JDS project on opensolaris.org)
I know SUN will merge changes back (the ones they like ) back into
Solaris at some point, but is the necessary also true ?
Finally , has SUN committed to maintaining ABI compatibility between
Solaris 10 (and later releases) and SXCE/SXDE/OpenSolaris.
Sun has committed to ABI compatibility between all Solaris releases,
SXCE/SXDE are no different. Sun can't commit to maintaining ABI
compatibility in OpenSolaris, since Sun doesn't have complete control,
but certainly hopes the OpenSolaris community continues to maintain
ABI compatibility where appropriate.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
