From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-2.8 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 991D420248 for ; Wed, 13 Mar 2019 15:12:13 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id DBD8B1218D0; Thu, 14 Mar 2019 00:12:09 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 06C991218AB for ; Thu, 14 Mar 2019 00:12:07 +0900 (JST) Received: by filter0168p3mdw1.sendgrid.net with SMTP id filter0168p3mdw1-7021-5C891DC6-22 2019-03-13 15:12:06.653441049 +0000 UTC m=+143844.351350793 Received: from herokuapp.com (unknown [3.80.34.250]) by ismtpd0036p1iad1.sendgrid.net (SG) with ESMTP id nC8O38c-QmWWXqp4-OiS5Q for ; Wed, 13 Mar 2019 15:12:06.510 +0000 (UTC) Date: Wed, 13 Mar 2019 15:12:06 +0000 (UTC) From: nagachika00@gmail.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 67262 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15617 X-Redmine-Issue-Author: sam.saffron X-Redmine-Sender: nagachika X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?O2wxg26uOO6cft6GjkEp=2FGevTnH9lR=2FEdG60AX3F8=2FDOfnFrYowCkktwxj+LTU?= =?us-ascii?Q?=2FbrqRIablGNlYKeBrqtO+jVhPT0PKGeT6d2jSsx?= =?us-ascii?Q?GTi7KGX1Uzgil8z=2FQoJDCY0dQur908ON9hsA96y?= =?us-ascii?Q?pKVNLUO1bttv=2FW=2FX7LNNfANNUeD+aSPte2ncarB?= =?us-ascii?Q?N5+LMetEFfN7uCSwOL4Vo0b7MuJiXnpemdA=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 91810 Subject: [ruby-core:91810] [Ruby trunk Misc#15617] Any chance we can ship 2.5.4 sooner rather than later? X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" 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/