Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 82164 invoked from network); 13 Sep 2000 20:53:20 -0000 Received: from sm3.texas.rr.com (24.93.35.210) by locus.apache.org with SMTP; 13 Sep 2000 20:53:20 -0000 Received: from localhost (cs16774-173.austin.rr.com [24.167.74.173]) by sm3.texas.rr.com (8.10.1/8.10.1) with SMTP id e8DKrqP07852 for ; Wed, 13 Sep 2000 15:53:52 -0500 Message-Id: <200009132053.e8DKrqP07852@sm3.texas.rr.com> To: cocoon-dev@xml.apache.org Subject: Re: [1.8] Let's get this right Date: Wed, 13 Sep 2000 15:53:18 -0500 From: Michael Engelhart reply-to: mengelhart@earthtrip.com x-mailer: Apple Mail (2.317) X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > what we've done in the past is once the code is pretty stable and we want > to release, stefano tests it under apache/win, i test it under > apache/linux, and if everything seems fine, we push it out. sure, a more > formal testing procedure would be nice, but we haven't exactly been > swamped with offers by highly responsive people to test on other platforms > - nor do we have much of a test suite. > Interesting though. What would everyone envision a test suite should have in it's bag of tricks. Maybe between all of us we have enough code to create a test suite if we could define what it should/shouldn't do. Mike