Tim & Jon,
I need signatures from both of you as project managers to
approve the contract below allowing Live Upgrade to use the project
private sparse file support that is being added to cpio. Please
respond to this message saying that you approve the contract, or let me
know what changes need to be made before you can approve the contract.
Cheers,
Don
@(#)contract 1.8 @(#) /shared/sac/arc/ARC-Templates/contract [1.8 06/12/06]
CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES
0. Number: PSARC/2008/727-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: ON
Department or Group: Solaris Interfaces
Bugster Product/Category/SubCategory: solaris/utility/archiver
Responsible Manager: Tim Sparlin
3. The CONSUMER is identified by the following:
Product or Bundle: Live Upgrade
Consolidation: Install
Department or Group: Live Upgrade
Bugster Product/Category/SubCategory: solaris/solaris_install/live_upgrade
Responsible Manager: Jon Bowman
4. The INTERFACES are:
cpio -H odc_sparse
5. The ARC controlling these INTERFACES is: PSARC
6. The CASE describing (Exporting) these INTERFACES is: PSARC/2008/727
7. The following SPECIAL ARRANGEMENTS are made which modify the rules
imposed by the stability levels listed in section 4 above:
_N_ 7a. Although the stability level doesn't normally restrict it,
SUPPLIER promises to only modify INTERFACES in an incompatible
way as follows:
_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:
_N_ 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:
[In particular, include whether the SUPPLIER will inform the
CONSUMER or obtain approval of the change from the CONSUMER.]
11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
follows:
12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
follows:
13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
tested as follows:
14. SUPPLIER and CONSUMER agree that this contract can be terminated as
follows:
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: Date:
For CONSUMER: Date:
For ARC: 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:
