Pegasus Enhancement Proposal (PEP)

PEP #: 091

Title: Adding Fields to PEP Template to pick up Platform Issues and Testing

Version: 1.0

Created: 29 July 2003

Authors: Karl Schopmeyer

Status:  Approved

Version History:

Abstract:

Definition of the Problem

1. Subsequent to the usage of PEPs as our controlling process we have had a problem several times whereby new functionalities that are to be put into Pegasus are defined in general, installed in general, but not complete for all ported platforms.  Thus as an example, the logging functions were complete except that there were some specific platform functions and for windows these were simply stubbed by the logging developers.  It was only in testing later that the existence of these stubs was discovered.

2. We have not clearly identified the requirements for testing on the Pegasus Platform while at the same time we all feel that we are committed to building automated tests for everything we do.  This subject often gets side tracked and not discussed in the rush of reviewing and approving PEPs.

Proposed Solution

1.  Platform Issues

I propose simply that we add a new section to the PEP Template defining any platform specific issues and any required platform specific implementation.  Done properly by the authors of the original PEP this will identify for the Pegasus community (and specifically the platform maintainers) if there is any platform specific limitations, any required platform specific code and allow the community to resolve the issue.

We propose adding the following section to the template:

Platform Specific Issues

<Please identify any platform specific issues OR any required platform specific code required. In particular, note any limitations that may require attention of platform maintainers including limits in testing or functions that may be stubbed for certain platforms or incompatibilities with any of the supported platforms

2. Testing

We propose adding the following section to the PEP template to insure that all PEP definers consider testing Issues

TESTING

<Define the extensions to tests or additional tests that will be implemented in the automated testing to test any functionality defined in this PEP.>

Rationale

Schedule

Discussion

<Additional information from discussions,  reviews, and decisions of the steering committee and architecture team can be recorded here. Information in this section is to help reviewers but MUST also be reflected in the Proposed Solution / Rationale, etc. sections. This section is for information only during the review process.>

Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group

Permission is hereby granted, free of charge, to any person obtaining a copy  of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.