From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 506B519E0068 for ; Thu, 31 Dec 2015 03:28:16 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id BF876B5D836 for ; Thu, 31 Dec 2015 04:00:58 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id CE9C618CC7B6 for ; Thu, 31 Dec 2015 04:00:58 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id ABAD3120613; Thu, 31 Dec 2015 04:00:56 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from mail-yk0-f178.google.com (mail-yk0-f178.google.com [209.85.160.178]) by neon.ruby-lang.org (Postfix) with ESMTPS id 3B9BD12060C for ; Thu, 31 Dec 2015 04:00:51 +0900 (JST) Received: by mail-yk0-f178.google.com with SMTP id x67so161552336ykd.2 for ; Wed, 30 Dec 2015 11:00:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=KsyWxIIxT6qgcL8xKxzkYMHfEktRyrulZMsrS8a4pEU=; b=d+9WZxO94cGc1r0oa799r5mWdd8YRGTvTQAB0iI3+XC8K0hENqwICPzKU/p/TPWkSv oY3iSxVGaZ05TwpPlB70u6/3l34CUo2ZDhq4C7l8LMjjA9qNRB4v95N+wdmyEP/U0Jvr j1/Xdsd3AMb0dnZ7UhiPYAs8u/NYiV7A0cuAiblO6suXH+mOZtprvCCRCrtt1DWn3WCl vkCVLBhXS96ou8y2qU6Z71wmcJjdUOfpIUs37qzrRL5xrhdAzP46QsThSwCuYRJXJ4DB NWcYPUx+ItR+bU+CE00SVsH71k/QB1RywrwjXC+onNmAQA2hwmGDu6+2OeK2H6GKL3u8 AHJg== X-Received: by 10.129.145.143 with SMTP id i137mr16983013ywg.268.1451502048871; Wed, 30 Dec 2015 11:00:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.3.198 with HTTP; Wed, 30 Dec 2015 11:00:09 -0800 (PST) In-Reply-To: <20151227044537.GA31924@dcvr.yhbt.net> References: <20151227044537.GA31924@dcvr.yhbt.net> From: "NARUSE, Yui" Date: Thu, 31 Dec 2015 04:00:09 +0900 X-Google-Sender-Auth: sjcFfBQdm79-SRtWaVb4hCnam1c Message-ID: To: Ruby developers X-ML-Name: ruby-core X-Mail-Count: 72622 Subject: [ruby-core:72622] Re: Ruby 3.0 in 2017? 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" As far as I understand, 1. Matz decides the version to be released. 2. Current trunk is version 2.4, but it doesn't mean 2016-12-25's release is 2.4. It may change to 3.0 in 2016. 3. Ruby 3.0 must be 3 times faster than Ruby 2. (Ruby 3x3) This means 3.0 won't be released before it. 4. Ruby understands incompatibility needs sufficient benefit. 2015-12-27 13:45 GMT+09:00 Eric Wong : > It looks like we'll be working on Ruby 2.4 this year for a Christmas > 2016 release. So I guess we won't have Ruby 3.0 won't landing until > Christmas 2017 at earliest? > > For what it's worth, I do not look forward to ever having a > backwards-incompatible flag day for 3.0. Too much has been done > since 1.9 came out to break compatibility. > > From a non-Pythonist point-of-view, Python's 2-to-3 transition looks > like a complete mess. As a long-time (and still daily!) Perl 5 user; > I'm happy to see continued improvements to 5 and don't care at all > for 6, yet. > > Unsubscribe: > -- NARUSE, Yui