> Last I heard, the plan is for SXDE to go away and be replaced by
> Indiana.  SXCE, on the other hand, should stay.

SXCE should continue until it's no longer needed.  In my mind, there
are a number of things any proposed SXCE replacement needs to do in
order to be *the* replacement including:

        1) Implementing all the existing, ARCed functionality of the
        existing SXCE release (note that some of that functionality may
        be available via a package repository rather than on the media
        itself).  Any existing functionality which isn't going to be
        available in the replacement needs to have been properly EOLed
        and then EOFed.

        2) Obviously, any other changes to interfaces between SXCE and
        its replacement need to be ARC approved as well.

        3) There needs to be sufficient means to test the replacement.
        For example, hands-off installation via something like
        JumpStart needs to exist before SXCE can go away since that
        type of technology is used for running automated tests, build
        by build.

        4) There are obviously other criteria as well that needs to be
        defined and then adhered to in the areas of quality,
        performance, etc.

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

Reply via email to