Re: wait_reading_process_ouput hangs in certain cases (w/ patches)

[Stefan Monnier]

> Please excuse my bluntness (not meant as an offense or anything alike)
> but that argument does not really hold up. Imagine we were working on a
> filesystem, found a longstanding corruption bug that could randomly hit
> everyone and silently corrupt data every once in a while (or never). It
> gets discovered, fixes are ready but those won't get committed since
> the bug has been around for ages, so it can wait a bit longer until the
> fixes have been through another timely major release cycle.

AFAIK we're talking a bout hangs (and hangs you can interrupt with C-g
AFAICT), not about data corruption, so the comparison is unfair.

> I still think fixing actual bugs is more important than holding those
> fixes back for longer due to the off-chance of introducing new ones.

> And again: Isn't that what beta release are for? Finding bugs and fixing
> them before the actual stable release?

They're for finding&fixing *regressions*, and I think this bug doesn't
fall into that category.

> I'm not arguing for rushing those fixes out in a 25.3.x release or
> whatever. But the 26 beta cycle seems more than appropriate to me as
> its a new major release... just my 2ct.

My recommendation is based on the premise that 26.1 is due Real
Soon Now (with at most one more pretest before the release-candidate).

> And I promise I will shut up now about this if nobody agrees with me. :)

I don't fundamentally disagree: it's a balancing act.


        Stefan