Martin Bochnig wrote:
> I still don't know very much about your actual plans with SPARC (server 1.3 
> vs. 1.5 vs. 1.5.1++).

My plans for SPARC are the same as x86.   Continue to ship 1.3 for now,
switch to 1.5.1 starting around build nv_104 or so.

> 2008.11 vs. 2009.04?
> There is no attempt to tell me (or the users) what's going on in terms of 
> SPARC-Indiana. You are neglecting your most loyal previous customers, and by 
> doing so you ensure, that "previous" and "future" are going to be disjoint 
> (disjunkt) sets.

I thought that had already happened on indiana-discuss and other, more relevant
mailing lists.   I know it was covered on the Commmunity Town Hall a couple
weeks ago - you can see that SPARC has moved from "2008.11" to "future" in the
slides in the "Overview & Updates" link on
http://www.genunix.org/wiki/index.php/Indiana#OpenSolaris_Community_Town_Hall_Meeting
or listen to the MP3 recording on that page.

> You wanna make "your own" sunny thing. From time to time you report (!, 
> one-directional) what you already have decided to do. This has nothing to do 
> with project "FOX" any longer, as it had been proposed by the (true) 
> community in 2006. It's simply the successor to your old consolidation, with 
> the difference that is is based on 100% open-src components now, rather than 
> on your internal closed-src Xsun tree. But it is the direct and total 
> successor to the xwin-consolidation, so it is not an actual "Open Opensource 
> Project" at all:

I never intended for the FOX gate to replace the X consolidation, but to be a
project to merge the three code bases, and eventually merge back into the X
consolidation, which would then be managed as an open consolidation like ON &
JDS and other ones will be.    Exactly when and how, I don't know yet.

> Question: Would it be imaginable to ship both the 1.3 and 1.5.x series 
> servers at the same time on SPARC, at least for some time until 1.5.x really 
> works with misc. legacy drivers?

Imaginable?  I suppose - I hadn't thought about it.  It would take
packaging them so that they use different paths for all their loadable
modules and such.

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering


Reply via email to