Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: Setup testing From: Robert Collins To: cygwin-developers AT cygwin DOT com In-Reply-To: <20011031174758.B28365@redhat.com> References: <1004523522 DOT 1521 DOT 37 DOT camel AT lifelesswks> <20011031142725 DOT A10174 AT redhat DOT com> <1004568440 DOT 1521 DOT 146 DOT camel AT lifelesswks> <20011031174758 DOT B28365 AT redhat DOT com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 01 Nov 2001 10:33:34 +1100 Message-Id: <1004571220.1701.162.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 31 Oct 2001 23:37:53.0895 (UTC) FILETIME=[0FC62F70:01C16265] I think it's time we got a little wider testing done for setup.exe... here's what I'd like to do. 1) have a snapshot of setup.exe included on the cygwin snapshots page, built when a cygwin1.dll snapshot is built. 2) Ask for limited (ie they email (say) me first) user testing and feedback. I'm not interested in provoking a feedback storm on the cygwin mailing list, but I think that 'idiot user' feedback is needed - even though we aren't quite happy ourselves yet. 1) Should be a trivial change to Chris' current snapshot script, and 2) I'm happy to have as my problem :} Rob