> 4 months we have been stuck on build 134, "4 months!"
> I don't call this progress, at this rate Oracle will
> have to push Solaris 10 out to update 40 before
> Solaris next is ready. The patch bundle for Solaris
> 10 is now so large that it takes 4 hours to patch
> from update 6 to update 8. Solaris next delay is not
> only hurting the Open Solaris community but is also
> hurting the Solaris community by making it impossible
> to apply a patch bundle inside a maintenance window.
> Yes It may be what Oracle has been saying all along
> but they have been saying it 4 months without a drop
> of progress. There is only two weeks left in First
> half of CY2010.

I think the reason why we have been using  build  134  that long is because the 
next stable release of opensolaris will be from  build 134 and oracle wants to 
get it right before it's availabe for download,  it appers they are alredy 
working on respins of build 134 in the form of build 134a and 134b. 134b  may 
be used for  the next realease.  I don't have a link to the site but I remember 
 reading a while back that solaris 11 was going to be based from opensolaris 
snv_134. I have seem this type of postponements before e.g. freebsd 5, i think 
it was in development for three years before it was released, etc 

"Builds 134a & 134b are respins of build 134 to fix stopper bugs for the 
OpenSolaris 2010.03 release.   In the main Nevada branch, these fixes 
integrated in later builds."

http://hub.opensolaris.org/bin/view/Community+Group+x_win/changelogs-nv_130
-- 
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to