Phil Sainty <***@orcon.net.nz> writes:
If the bugs are in new functionality, I wouldn't see any issue with
leaving the improvements until the next release if necessary; but
I would have thought known regressions to behaviour which was working
properly in the previous stable release would be worth delaying the
new release to fix, if necessary.
I suppose I don't understand why there's any hurry to release 26.1.
Because it wouldn't be released ever, otherwise. The Emacs bug tracker
contains 1742 open bugs in state "serious,important,normal" as of
today. I bet there are many open bugs we could apply the same reasoning
as you have given above.
Emacs 26.1 is in code-freeze. Bug#31355 does not block Emacs 26.1, and a
workaround (your patch) does exist. So I don't believe this bug shall
stop the release.
But I'm neither the maintainer nor the release manager, which will
decide. Eli? John? Nico?
Best regards, Michael.