X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F160D3840C24
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis: v=2.3 cv=OubUNx3t c=1 sm=1 tr=0
 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
 a=IkcTkHD0fZMA:10 a=ohXXrwaOYK99BznRwQsA:9 a=QEXdDO2ut3YA:10
Subject: Re: coreutils refresh request (again)
To: cygwin AT cygwin DOT com
References: <DM6PR09MB40437374A8AB3F57B21D349DA58D0 AT DM6PR09MB4043 DOT namprd09 DOT prod DOT outlook DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Autocrypt: addr=Brian DOT Inglis AT SystematicSw DOT ab DOT ca; prefer-encrypt=mutual;
 keydata=
 mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
 PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
 AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
 WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
 BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
 IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
 RSyTY8X+AQ==
Organization: Systematic Software
Message-ID: <25eb3e03-9982-5e50-d40c-f82f3bdb9c57@SystematicSw.ab.ca>
Date: Thu, 4 Jun 2020 07:56:58 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <DM6PR09MB40437374A8AB3F57B21D349DA58D0@DM6PR09MB4043.namprd09.prod.outlook.com>
Content-Language: en-CA
X-CMAE-Envelope: MS4wfAyOvdo+9mh/L0Y0EGEFovzRGABRvdQuEfiaFaa5azcqIDFJ2I7oTEbniDqEwM0ZM2HgkQZYhlzKNODxWGWXFffg1EQXVRzBOrqfpp43UQ7cI07lziHG
 2jLOUhkGa9VqUEKWjuvf3xR+WpNOeXn1IEnYktwnTy7iQ1t9jR+ni4YWBMlDuEMjjN8LXgLfG7FIiQ==
X-Spam-Status: No, score=-11.6 required=5.0 tests=BAYES_05, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2020-05-31 08:52, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> Having upgraded my Cygwin install today, I still see the old coreutils
> package v8.26, from 2016.
> Looks like the current version is now 8.32, released in March this year.
> Can Cygwin please get this updated?

Upgrades, especially of a multi-program package, are not always easy, with many
features added each release, and often bugs, sometimes Cygwin specific.
The volunteer maintainers may have to negotiate with upstream maintainers about
whether they can get bug fixes made upstream, or bug fixes or feature support by
other Cygwin library or package volunteer maintainers, or their upstream
maintainers.

All of these people are busy with work and life: many volunteer, and some also
work, on multiple projects; some may have been or are now sick (hopefully few to
none), or have conditions or illnesses which make them unable to contribute
temporarily.

Some core volunteers on this project also have jobs at RedHat (which supports
the infrastructure) and was bought by IBM, who is once again betting the company
on a new direction, so some volunteers may now have limited or no time for other
projects.
One such volunteer maintainer of over 2500/25% of Cygwin packages has had to
give them all up due to having no time to spare now.

Add to that the current pandemic issues, particularly badly handled in some
major Western countries, and perhaps users could be somewhat patient and
understanding of the situations of volunteer maintainers, who may now be working
remotely, likely overtime to support volumes of issues or scaling.

Developers who are corporate (or personal) users could think of contributing to
the project by maintaining packages they use and are interested in (2500+ are up
for grabs), spreading the load, or get some of their corporate IT development
staff to help them and their organization out by doing upgrades to packages they
need or use, and contributing those upgrades to the project.

The Cygwin cygport package build infrastructure is an extensive and professional
job and takes care of a lot of the upgrade mechanics, but build failures need
thought and work to diagnose and generate a fix, submit patches upstream, decide
whether to wait for an upstream patch to land, or release sooner with a Cygwin
patch, bearing in mind that Cygwin is only a minor volunteer blip in the
otherwise fairly well funded software distribution ecosystem.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple