[#92063] [Ruby trunk Misc#15723] Reconsider numbered parameters — zverok.offline@...
SXNzdWUgIzE1NzIzIGhhcyBiZWVuIHVwZGF0ZWQgYnkgenZlcm9rIChWaWN0b3IgU2hlcGVsZXYp
3 messages
2019/03/31
[ruby-core:91810] [Ruby trunk Misc#15617] Any chance we can ship 2.5.4 sooner rather than later?
From:
nagachika00@...
Date:
2019-03-13 15:12:06 UTC
List:
ruby-core #91810
Issue #15617 has been updated by nagachika (Tomoyuki Chikanaga). I'm sorry the link in previous post was for Japanese. English version is here. https://www.ruby-lang.org/en/news/2019/03/13/ruby-2-5-4-released/ ---------------------------------------- Misc #15617: Any chance we can ship 2.5.4 sooner rather than later? https://bugs.ruby-lang.org/issues/15617#change-77084 * Author: sam.saffron (Sam Saffron) * Status: Closed * 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>