Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<04CAD2CF7C2CD51199C7009027AD078B8D05B6@ev003msxaege.ae.ge.com>
From:	"Fletcher, Bob (GEAE, EB&TS)" <bob DOT fletcher AT ae DOT ge DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	Are there good and bad times to download a copy of Cygwin?
Date:	Tue, 11 Jun 2002 11:53:21 -0400
MIME-Version:	1.0

We have a group of people using the Cygwin command line tools (not compilers).
Because we all want to use the same copy,  I do a "download from internet" and
make the copy available to everyone. We try not to upgrade two often to avoid
the effort of testing new versions. In this scenario, I want to make sure that I
get a good, stable copy.  

Are there "better" and "worse" times to take a copy of cygwin?   ( It's always
"good" to download cygwin :)   Some Open Source  tools have even and odd
numbered releases that tell you something  about the stability of the release. 

Do you think that it's better to grab a copy just before the release of the new
cygwin.dll  ( and be stuck with an old copy) , or just after ( and be stuck with
a buggy copy) ?


Bob.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -