On 04/28/10 14:12, Frank Middleton wrote:
Understood about the release management overhead, but by running so far ahead, aren't you losing out on the feedback provided by those of us who try to stay up with the development releases? We've gotten some "fixed in b137" messages which are really tantalizing :-).
To a degree... now that svr4 versions of Nevada are no longer available, internal testing has increased significantly.
IIRC the "point of no return" issue has been discussed before, but could you refresh us on what that is? If we're already on b134, are you suggesting we have to go to 2010.03 before b135? We've never actually installed a non-dev release, at least on on SPARC...
If you're on dev and upgrade to a release after 134, the only way to install 2010.03 will be to boot an older BE, since 2010.03's build version number will be somewhere between 134 and 135. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
