From: shevegen@... Date: 2019-02-26T17:58:59+00:00 Subject: [ruby-core:91625] [Ruby trunk Misc#15617] Any chance we can ship 2.5.4 sooner rather than later? Issue #15617 has been updated by shevegen (Robert A. Heiler). 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). ---------------------------------------- Misc #15617: Any chance we can ship 2.5.4 sooner rather than later? https://bugs.ruby-lang.org/issues/15617#change-76888 * Author: sam.saffron (Sam Saffron) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- We started carrying code like this in Discourse due to #14634 breaking Queue after fork. https://review.discourse.org/t/dev-disable-async-logging-in-development-on-broken-ruby/1829 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 -- https://bugs.ruby-lang.org/ Unsubscribe: