X-Spam-Check-By: sourceware.org
Message-ID: <44972404.47FC564F@dessent.net>
Date: Mon, 19 Jun 2006 15:24:04 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Latest Cygwin Release 5 month old...
References: <002401c690e2$6f2656b0$0a3b6080 AT joehome> <449208C4 DOT 4CF28807 AT dessent DOT net> <4495C806 DOT 2020805 AT tlinx DOT org> <4495D125 DOT 4693156F AT dessent DOT net> <44971306 DOT 8030109 AT tlinx DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Linda Walsh wrote:

>     Nobody like to hear "oh, it's fixed in the latest build, but
> not in the released product."

Whether they like it or not doesn't change the situation at all.  The
fact remains that very often reported problems are fixed in snapshots,
so saying "try a snapshot first" is a very effective way to save a lot
of time on the part of both the person with the problem and the people
on the list that take the hours out of their day to try to help.  And
isn't that the goal of everyone posting to the list with problems, to
resolve them quickly?  This is a single DLL file we're talking about,
not a linux kernel, and it takes seconds to replace and doesn't require
a reboot.

>     If a developer doesn't think it is good enough to release,
> then I'm not sure I want to be testing on my "production" machine.
> Not everyone has a spare test machine.

That kind of logic is toxic poison to an open source project.  How do
you think those releases come to be?  If you want stable releases then
you need to regularly test snapshots and give feedback, otherwise the
releases will not be of high quality.  This is all a volunteer effort
here, and the developers' only way of assessing whether their fixes are
effective and stable is by hearing from people on the list that try
them.  If everyone played the "I'm not going anywhere near something
that doesn't have the mythical release stamp of approval" card then no
forward progress would ever be made, and you'd have a lot of really
buggy releases.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/