DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51MBSiGM1375379
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E60473858D20
To: cygwin@cygwin.com
Subject: Re: Making a Cygwin 3.5.8 release? Fwd: All sparse file fixes
 available in cygwin-3_5-branch?
In-Reply-To: <CALXu0UckhFdoJ1gsgmKq3CJ61+BKxr4nCqD2GbQoXTQ=1FQ-iw@mail.gmail.com>
 (Cedric Blancher via Cygwin's message of "Sat, 22 Feb 2025 08:17:00
 +0100")
References: <CALXu0Ud9WJUfS2YgZNbAOBfs3u=27E+4c3tOSYkSApx08_1-Cw@mail.gmail.com>
 <Z7Rmrl3tmQ5NjGAc@calimero.vinschen.de>
 <CALXu0UdHm0uZjBqL0BaZw59KkM03wViHih5Qyc8WS0hinGraQg@mail.gmail.com>
 <CALXu0UfQTmBMkB3Nt=+5vS-XazUaKuqgk7Tpa=5rO=W2FoXWJQ@mail.gmail.com>
 <c13a115a-470c-4968-bebe-cbf5c9d2cf3f@SystematicSW.ab.ca>
 <CALXu0UckhFdoJ1gsgmKq3CJ61+BKxr4nCqD2GbQoXTQ=1FQ-iw@mail.gmail.com>
Date: Sat, 22 Feb 2025 12:27:26 +0100
Message-ID: <87r03qz0bl.fsf@Gerda.invalid>
MIME-Version: 1.0
Precedence: list
From: ASSI via Cygwin <cygwin@cygwin.com>
Reply-To: ASSI <Stromeko@nexgo.de>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

Cedric Blancher via Cygwin writes:
> We are VERY concerned that this plan will backfire. Basically nothing
> here works right now, and we are still trying to determinate the root
> causes. Plural. Too many bugs.

I've said it before, but if you really didn't recognize it until now:

Cygwin is a following a rolling release distribution model, which means
it can literally break at any time and for any length of time.

Now, I've also used (and am still using, albeit on a smaller scale)
Cygwin in a corporate / production environment (which I belive is what
you are talking about when you say "here"), so these things are in my
view necessary to even think about such a deployment:

 - independent (internal) access to all sources and binaries
 - a separate test and build environment
 - periodic test builds of packages and Cygwin itself
 - full control over the package selection including version locks and
   the ability to roll back single packages or even full installs

In the above scenario you could either decide to hold off on an update
or fork and fix it yourself.  If you can't do either of that, then sorry
to say: this is first and foremost your problem and you get to keep the
broken pieces.  Secondly, correlation is not causation; you have AFAICS
not yet shown that there is a bug in Cygwin.  Even if there was, you
still do not get to command what the project does to handle that
situation.  If you want to help it along, at least send actionable bug
reports, reproducers would be better, better yet would be patches.
 

Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

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