I originally wrote the following to explain the transition to our
team, and it's been shared with wider and wider audiences internally
since then.   I've had several people suggest I post an external
version to explain to the community and users at large what's changing.

I've modified it to use the external sites/terms, dropped some internal only
details like WebRTI usage, and to incorporate pointers to the revised ON IPS transition schedule Liane posted this week - I know she's working on
docs for the IPS transition that overlap a good deal of this, but
this focuses on the nearer transition off of SXCE.

Anyone have any suggested changes before I mail this off to
opensolaris-announce?   Any details of non-desktop bits that
should be covered in there with Xsun & CDE?

        -alan-

-------- Original Message --------

Subject: Nevada: What's going, what's staying, what's changing, what's not

What's changing at build 131:

    - The OS install images will only be available in IPS packaged formats.
        This means installs will be done via LiveCD (x86) or Automated
        Installer (SPARC or x86) - the old Install DVD, network install,
        jumpstart, and live upgrade all rely on the SXCE/SVR4 packaged
        images, which will not be available after build 130.

    For X, there's one additional wrinkle that doesn't affect most other
    consolidations - we've not packaged Xsun or the legacy SPARC graphics
    drivers in IPS format, so once this changeover is done, SPARC
    platforms will only have Xorg, and only have the graphics drivers for
    astfb (AST2000, 2100), efb (XVR-50, 100, 300), and kfb (XVR-2500).

    CDE has similarly only had IPS conversions done of the packages for
    the non-EOF portions (Motif, Tooltalk, dtksh, etc.) and most of the
    CDE desktop applications & environment will go away in the transition.

What's not changing at build 131:

    - Build schedules - still every two weeks (except at holidays), still
        following the same Nevada build schedule and build sequence - the
        builds continue to be numbered "snv_131", "snv_132", etc.

        See http://hub.opensolaris.org/bin/view/Community+Group+on/schedule

    - Bug tracking - the release is still "solaris_nevada", and the builds
        have the same names as before.   Developers won't start ignoring
        all "nevada" bugs, but bugs that only affect the SVR4 install
        methods (live upgrade, pkghistory, postinstall scripts, etc.) may
        be closed as will-not-fix once the changeover happens.

        Bugs for most of the OS should still be filed into Sun's bugster
        database via the http://bugs.opensolaris.org/ website, though
        IPS and Desktop bugs should be filed in the bugzilla database at
        http://defect.opensolaris.org/

    - Code repositories - the Nevada gates/repositories for all the
         consolidations will still be used - onnv for ON, XW_NV for X,
        sfwnv for SFW, etc.

    - The packages created by building the code - for the next few builds,
        all consolidations will continue to generate SVR4 packages for their
        builds, and the IPS team will continue to convert them to IPS, just
        as they have been since the IPS builds started for the first
        OpenSolaris release.

        ON will be changing generate IPS packages first, after the 2010.03
        release of OpenSolaris, as noted in:
        
http://mail.opensolaris.org/pipermail/on-discuss/2010-January/001461.html
        
        The rest of the consolidations will change in later builds, once
        we see what issues ON hits, and the necessary infrastructure is
        in place for delivering IPS packages from consolidations to the
        central Release Engineering repository.  X, Desktop, & SFW are next
        in line after ON, and have been working with Liane & the ON/IPS team
        on planning for our changeovers.

_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to