On Tue, 24 Sep 2002, Davis, Todd C wrote:
> How are patches like this and other changes to PCP tested and verified to be
> correct? I think enterprise class system utilities like PCP require a much
> higher level of qualify assurance than the typical open source project. What
> verification procedures does SGI go through before making a source tarball
> release? I think test suites should be made available to developers to use
> when making enhancements and bug fixes so changes can be verified. Tests
> could also be submitted with any enhancements before being accepted by the
> PCP project. Test suites can also be useful in verifying an installation of
> PCP.
PCP has a suite of approx 600 scripts for testing and quality assurance
(QA) - this suite was originally developed for the proprietary version of
PCP on IRIX over many years, and has been ported to Linux but has not
been released open source. Although it's a reasonable request, the work
to release it open source would be hard for me to justify.
In any case, I always run the QA suite before shipping any open source
PCP release. Given it's been so long since the last release, I think I'll
merge Mike's patch, run the QA suite and then ship a "release candidate"
for testing. This might not happen until next week because I also have
to deal with some minor legal issues associated with accepting Mike's
patch.
thanks
-- Mark
|