DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=NsfDo4M/Q/DOXTqCH3onWK2WNtO+R
	eIFssY1xNgAiePwngRBgH0ZpoNGaa4m30SJQUifOsYxL/ELhrtlezcpJUjWeKmSM
	S6r7qSV36MRNkJjJxbmx9By4mWUjV47/qALAUb1+6gwyWALz1HASsqPkJJxCF352
	QHdAMjac5Rx2oU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5e3ccb09.1c69fb81.a29f4.43ab@mx.google.com>
Date: Thu, 06 Feb 2020 18:27:21 -0800 (PST)
From: Steven Penny <svnpenn AT gmail DOT com>
Subject: Re: [ANNOUNCEMENT] Updated: gcc-9.2.0-1 (x86/x86_64) (Testing)
To: cygwin AT cygwin DOT com
References: <0216baa3-a6b4-839b-a678-cdf4e9c3f7b7 AT gmail DOT com>
Content-Type: text/plain; charset=utf8

On Thu, 6 Feb 2020 08:16:12 +0000, JonY wrote:
> I normally don't update mingw-w64 compilers unless the cygwin gcc has
> stabilized.
> 
> Do you need it ASAP? I can work on it soon if required.

I mean isnt that the whole point of Test packages? The way I see it the Test
package should always be matching the major version, and ideally the minor
version.

For even the test version to be literally 2 majors versions back kills any
reason to even have it. It would be better to just remove the test version
altogether and just have current and "prev" if it cant be kept up to date.
On a personal note the optics just look bad. GCC points people to Cygwin:

https://gcc.gnu.org/install/binaries.html

then when the users get here, they find the mingw64-x86_64-gcc-core 7.3 which
is 2 years old:

https://gcc.gnu.org/releases.html


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