From: Charles Oliver Nutter <headius@...>
Date: 2011-04-11T05:31:34+09:00
Subject: [ruby-core:35687] Re: [Ruby 1.8 - Feature #4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?

Good news, Shyouhei! This will help encourage us to move JRuby to 1.9
compatibility by default in the near(er) future.

- Charlie

On Tue, Apr 5, 2011 at 3:21 AM, Shyouhei Urabe <shyouhei@ruby-lang.org> wrote:
>
> Issue #4239 has been updated by Shyouhei Urabe.
>
>
> Hi, I happened to notice this being assigned to me. ��So I describe the status in short:
>
> "No core developers are currently willing to release 1.8.8."
>
> Core people are more and more getting interested in 1.9 development. ��Of course you can fork the project so it is technically possible for you to have YOUR OWN 1.8.8, but I think that would rarely happen. ��So it is almost certain, that there will be no 1.8.8.
>
> 1.8.7 support continues for a while, FYI.
> ----------------------------------------
> Feature #4239: Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
> http://redmine.ruby-lang.org/issues/4239
>
> Author: Shota Fukumori
> Status: Assigned
> Priority: Normal
> Assignee: Shyouhei Urabe
> Category: core
> Target version: Ruby 1.8.8
>
>
> ��###########################
> ��# This issue is translated from #4207.
> ��# For Japanese: This translation needs proofreading. If you have a patch, please send to sorah[at]tubusu[dot]net.
> ��# Newer version of translation available at: https://gist.github.com/b2c4f223d3ee0bca72ad
> ��###########################
>
> ��# http://redmine.ruby-lang.org/issues/show/4207
> ��= Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
>
> ��Hi,
>
> ��I know that we cannot release ruby_1_8 branch... more than anyone.
>
> ��But the time past 3 years from 1.9.0, and 2.5 years from 1.8.7;
> ��it will be turned to 3 years in June 2011.
>
> ��Why I'm marking "3 years," because releasing interval over 3 years
> ��first time ever, and almost systems have revised after 3 years from
> ��developed in my experience... so, almost codes which targets 1.8.7
> ��preparing to revised; I think.
>
> ��Well, Which version used when codes which targets 1.8.7 are revised,
> ��I recommend 1.9.2 on my post, but almost can't use 1.9.x in
> ��actuality. Like, Extension libraries doesn't work.
> ��When can't use 1.9.x in codes, so it means use only 1.8.7. but it is
> ��really tough, for making tasks with 1.8.7, and I think that when I
> ��can give up maintaining 1.8.7? when my motivation is decreasing in
> ��future, it won't increase again. So I want to use new version,
> ��and don't use 1.8.7. New codes must target newer versions.
>
> ��So, I want to set directions about 1.8.x future. I'm considing that
> ��destroy ruby_1_8 branch and we won't release 1.8.8 for a one of
> ��ideas. If we won't release 1.8.8, it means that can publish
> ��announcement about 1.8.7 is last version of 1.8 branch,then 1.8
> ��goes to last maintainance release. ah, in simplicity developers
> ��task is decreased; developers will be happy.
>
> ��P.S.: I hope that people in a posision like Endoh Yusuke at 1.9.2.
> ��Anyone?
>
> ��###
> ��# http://redmine.ruby-lang.org/issues/show/4207#note-6
>
> ��Well, Organize this issue without my factors, currently we have the following
> ��issues of 1.8.8.
>
> ��* the time past 3 years from 1.9.0 released. In last 3 years, We released
> �� 1.9.2 smoothly at 1.9 branch. Thanks Yugui (Yuki Sonoda).
> �� Also many users are using 1.9.x at forms of RailsDevCon.
> �� http://railsdevcon.jp/RailsDevCon2010report.pdf
> ��* 1.8.8 (and 1.8.7?) is on migration step to 1.9, but if we continue
> �� developing 1.8.8 at this rate and release 1.8.8 in 2020, do users which
> �� haven't migrated to 1.9 exist?
> ��* Currently does ruby_1_8 include any prompting structures to migrate
> �� 1.9.x more than 1.8.7 at all? Just not merged same patches as 1.9?
> ��* "I want to release so I release. Any users didn't effect." is a one of
> �� views, but it makes unhappy by recognition differences?
>
> ��So.. Because 1.8 mustn't let be uncontrolled,
> �� I propose the following ideas which possible:
>
> ��1. Not today but ASAP, release 1.8.8 as "better 1.8.7." Release goal is this
> �� ��Summer.
> ��2. Develop 1.8.8 until it's approached to ideal. Users can't be affect.
> �� ��Release goal is 2020 Christmas.
> ��3. We won't release 1.8.8 never. Drop.
> ��4. Otherwise I haven't thought yet.
>
> ��I don't specify any idea for adoption.
> ��Anyhow, I think that 1.8 mustn't keep current principle, so I asking "What do we do?"
>
> ��Well.. what do we do?
>
>
> --
> http://redmine.ruby-lang.org
>
>