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: <5.2.0.9.0.20030127151439.03d79008@pop.nycap.rr.com>
X-Sender: billlist AT pop DOT nycap DOT rr DOT com
Date: Mon, 27 Jan 2003 15:23:45 -0500
To: Max Bowsher <maxb AT ukf DOT net>, cygwin AT cygwin DOT com
From: "William A. Hoffman" <billlist AT nycap DOT rr DOT com>
Subject: Re: Cygwin Release process
In-Reply-To: <009c01c2c63f$b1080f90$78d96f83@pomello>
References: <5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030127132032 DOT 031f91e0 AT pop DOT nycap DOT rr DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Well, if I am the only person with this opinion, then you are right.
I should stop complaining and burn a CD.   However, I suspect that I am
not alone in wanting a more stable cygwin.    It will be hard to prove my
case, as the folks that read this list and post to it, tend to
be more developer oriented, and are more interested in not missing
out on the latest features than having a stable platform.

There must be some reason that RedHat, Debian and all the major linux 
distributions have releases.   

I belive that if this were setup, and download stats were created, it would
be come the most common type of download for cygwin. 


-Bill



At 08:07 PM 1/27/2003 +0000, Max Bowsher wrote:

>If this is not good enough for you, then *just burn a CD*. There is no need
>to force this artificial 'release' policy on the Cygwin project.
>
>
>Max.



--
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/