James Carlson wrote:
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.
Thanks for the options. They will certainly have to decide whether
the second makes business sense for them and their customers.
(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. :-/)
In my case ignorance is bliss :)
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.
Thanks for the elaboration. This is why I said 'may'. I am also with
the understanding that a feature will *not* make it into Solaris 10
if it is not already in Nevada, which is why I consider Nevada a
leading
indicator. But as you say, it may not get backported, and I use the
term port since it is not just a simple cut and paste.
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.
It would be great to have something that describes or defines
this a little
better, including how a bug or an RFE for Solaris 10 actually
works through
the process and how it differs for a feature that is being added
to Nevada.
Thanks
Steffen
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
