Any chance we can ship 2.5.4 sooner rather than later?
We started carrying code like this in Discourse due to #14634 breaking Queue after fork.
I was wondering if there is any chance we can fast track a 2.5.4 release? This issue is quite severe cause there are quite a few forking web servers out there (puma and unicorn) so the failure mode is common in the wild.
#14634 is already backported
Updated by shevegen (Robert A. Heiler) about 2 years ago
I guess this may be up to the release manager; perhaps he is a little bit
busy right now. You could consider adding it to the next upcoming developer
meeting ( https://bugs.ruby-lang.org/issues/15614 ) to get feedback whether
there may be any other difficulties (or to distinguish whether your issue
was not yet noticed, which I guess may also happen every now and then,
holidays, busy weeks and so forth).