CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES

0.  Number: PSARC/2006/550-01

1.  This contract is between
        a SUPPLIER of INTERFACES and
        a CONSUMER of those INTERFACES,
    both of whom are entities within Sun Microsystems, Incorporated.

2.  The SUPPLIER (definer and/or implementor) is identified by the following:
    Product or Bundle: Solaris
    Consolidation: OS-Net
    Department or Group: Solaris System Interfaces
    Bugster Product/Category/SubCategory: solaris/shell/korn93
    Responsible Manager:

3.  The CONSUMER is identified by the following:
    Product or Bundle:            jds (Java Desktop System)
    Consolidation:                Desktop
    Department or Group:          Open Source BU600
    Bugtraq Category/SubCategory: jds/application
    Responsible Manager:          Leontine Binchy <Leo.Binchy@sun.com>

4.  The INTERFACES are:
      Interface Name             Classification     Comment
      fts_open()                 Contracted         
      (libast.so.1)              Project Private

      fts_close()                Contracted         
      (libast.so.1)              Project Private

      fts_read()                 Contracted        
      (libast.so.1)              Project Private

      fts_set()                  Contracted
      (libast.so.1)              Project Private

5.  The ARC controlling these INTERFACES is: PSARC

6.  The CASE describing (Exporting) these INTERFACES is: PSARC/2006/550

7.  The following SPECIAL ARRANGEMENTS are made which modify the rules
    imposed by the stability levels listed in section 4 above:
 
    

      
_Y_ 7a. Although the stability level doesn't normally restrict it,
        SUPPLIER promises to only modify INTERFACES in an incompatible
        way as follows:

        In an minor release of Solaris.

_N_ 7b. Although the stability level doesn't normally allow it, CONSUMER will
        expose INTERFACES to a PARTNER, which is external to Sun, namely:
                Name of Company:
                Name of Department or Group within Company:
                Responsible Manager:

_Y_ 7c. Although the stability level doesn't normally allow it, CONSUMER will
        import INTERFACES from a separate consolidation.

_Y_ 7d. If SUPPLIER decides to change (including replace or remove) any
        portion of the INTERFACES, SUPPLIER will notify CONSUMER of the
        proposed new version, no later than the application for ARC
        approval of the new version.
        If SUPPLIER and CONSUMER are contained in the same consolidation,
        they have the option of arranging for simultaneous conversion
        to the new interfaces.  If this is not possible, or if they are
        not in the same consolidation, then SUPPLIER will either make best
        effort to work with CONSUMER so that CONSUMER can detect which
        version of INTERFACES is being supplied, or else SUPPLIER will
        make best effort to supply both old and new versions of
        INTERFACES.
        If SUPPLIER cannot make both versions of INTERFACES available,
        and SUPPLIER and CONSUMER cannot devise a method whereby
        CONSUMER can detect which version of INTERFACES is being
        supplied, and the old version of CONSUMER will not run with the
        new version of SUPPLIER, then either the EOL process must be
        followed by SUPPLIER, or else a major release of SUPPLIER will
        be required, or the change will not be allowed.

8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make
   best effort to accommodate such changes, which shall then be
   treated in accordance with paragraph 7 above.

9. Notwithstanding paragraphs 7 and 8, a change to any portion
   of the INTERFACES shall be regarded as a completely new set of
   INTERFACES which require both ARC approval and execution of
   a new contract.

10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be
    handled as follows:
    SUPPLIER will notify CONSUMER immediately of any planned or 
    implemented change that may impact SUPPLIER's feature.

11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
    follows:
    These interfaces are documented by the PSARC Korn Shell 93 Integration case 
    (PSARC/2006/550).

12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
    follows:
    ARC material of PSARC Korn Shell 93 Integration(PSARC/2006/550).

13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
    tested as follows:

    CONSUMER will run smoke tests as part of regular testing to
    verify binary compatibility of provided interfaces.

14. SUPPLIER and CONSUMER agree that this contract can be terminated as
    follows:

    By mutual agreement by SUPPLIER and CONSUMER.

15. This contract is not valid until "signed" via agreement from the
    SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by
    this contract.  E-mail agreement to the contract should be archived
    in the mail archive of CASE; verbal agreement to the contract
    should be noted in the meeting minutes.  This contract remains
    valid until superseded or invalidated.

For SUPPLIER: Tim Sparlin       Date: 07/16/2008
For CONSUMER: Leo Binchy        Date: 07/16/2008
For ARC: John Fischer           Date:

    A copy of this contract shall be deposited in the CASE directory as
    "contract-<digits>" or in a "contracts" subdirectory.

16. (Not to be filled in until superseded or invalidated.)
    This contract was superseded or invalidated by CASE:
    For ARC:                    Date: