X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19CHlltZOBlk0sTt2xVm1fz
Date:	Sun, 19 Aug 2012 14:25:22 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Which version of cygwin 'rock solid'
Message-ID:	<20120819182522.GA23680@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CACgPhYo3QQno3VDTWeXMSnz4XSiGNCebSYeNTvntD8OXMEo3jw AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CACgPhYo3QQno3VDTWeXMSnz4XSiGNCebSYeNTvntD8OXMEo3jw@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Sun, Aug 19, 2012 at 01:17:24PM +0400, Andrey Khalyavin wrote:
>On 08/17/2012 04:13 PM, Devin Nate wrote:
>> My question, of the Cygwin users (or developers), which version would you select if your goal was maximum stability?
>
>Our experience is that they are all not particularly reliable (we
>haven't checked all 1.7.* versions though). If you want
>to make your script more stable, add retry logic and make it as more
>serial as possible.

The best way to achieve stability in Cygwin or any software project is
by offering up some effort and providing good bug reports and test cases
so that we can fix problems.  That would tend to make the latest version
the most stable.

Even better would be to gain understanding in how Cygwin works and offer
improvements yourself.

>Unless you want to create your own version of cygwin of course. You
>can try to backport all important crash and bug fixes
>to an older version. Then the most recent versions (1.7.15 and 1.7.16)
>are probably the best since backports will be easier.

That would be a continuing battle and it would also be rather selfish.
If you are going to gain enough knowledge to figure out what's important
and how to backport it you might as well do the rest of the world some
good too and help improve things for the real Cygwin project rather than
your fork of it.

cgf

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

- Raw text -