From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72503] Ruby 3.0 in 2017?
Date: Sun, 27 Dec 2015 04:45:37 +0000 [thread overview]
Message-ID: <20151227044537.GA31924@dcvr.yhbt.net> (raw)
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.
next reply other threads:[~2015-12-27 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 4:45 Eric Wong [this message]
2015-12-30 19:00 ` [ruby-core:72622] Re: Ruby 3.0 in 2017? NARUSE, Yui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151227044537.GA31924@dcvr.yhbt.net \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).