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=-3.1 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=ham 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 52BF720248 for ; Tue, 26 Feb 2019 17:59:08 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 2C3F4121AE8; Wed, 27 Feb 2019 02:59:03 +0900 (JST) Received: from o1678916x28.outbound-mail.sendgrid.net (o1678916x28.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 53574121AEB for ; Wed, 27 Feb 2019 02:59:01 +0900 (JST) Received: by filter0089p3mdw1.sendgrid.net with SMTP id filter0089p3mdw1-19327-5C757E62-2E 2019-02-26 17:58:58.712251959 +0000 UTC m=+214192.103770591 Received: from herokuapp.com (ec2-52-90-53-97.compute-1.amazonaws.com [52.90.53.97]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id n-o5rKxWSMeVr9X0JiqOsg for ; Tue, 26 Feb 2019 17:58:58.653 +0000 (UTC) Date: Tue, 26 Feb 2019 17:58:59 +0000 (UTC) From: shevegen@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 67075 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15617 X-Redmine-Issue-Author: sam.saffron X-Redmine-Sender: shevegen 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: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS7hAuDHPcaNvNgINUr1RoJVenhZ9LY71ME8wh PUgV1Nm/zpn7hp7nNBj4vbiQdfR9ABhmAcpIvqf8TwHCq1hUvhxFyemwvzfD1R/ai7GGJhCMhiCKMq nxwLbTw+hDagZNg8S/lSasa1amYBW3ciVWfPeQ4ktI34930IE+vNHak46A== X-ML-Name: ruby-core X-Mail-Count: 91625 Subject: [ruby-core:91625] [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 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/