Steffen Weiberle writes:
> Sure, understood. I am using them only as an indicator that something
> has been delivered into the build.
>
> So is this intended to only be used by Sun until there is more
> experience?
> Or is there a way ISVs can 'register' so that they are alerted to
> changes?
To do so, the ISVs can do two things:
- Get a Sun manager (perhaps in MDE) to arrange for an ARC contract
on these interfaces. A contract prevents Sun engineers from
evolving those interfaces -- it throws monkey wrenches into the
middle of projects -- until the migration path for the ISV can be
worked out. If the manager who owns the technology agrees, then
the interfaces will be locked down for the ISV's use, and proper
documentation can be part of the agreement.
- Get involved in OpenSolaris. Do the work right in ON, where no
contract is required.
(Yes, I understand that all of this ARC "contract" stuff is just
horribly broken in the OpenSolaris world. "Manager" means nothing.
Please don't flame on that problem. Start a new thread for it. :-/)
> Especially in S10, where changes in Nevada are a leading indicator of
> what may change in a coming update or patch for Solaris 10.
Nevada tells you really nothing about S10. They're separate gates
with separate procedures. Some things do get backported, but not
necessarily all of them, nor in the same order, nor even with exactly
the same features.
They're different. Please don't encourage people to think that
they're the same -- it results in hard to resolve misunderstandings,
such as requests for the "schedule" for when Nevada features will be
in S10. We have no such schedule to offer.
--
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
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
