Issue #4239 has been updated by Shota Fukumori.


#####
# This is translation from
# Akinori MUSHA's mail at http://redmine.ruby-lang.org/issues/show/4207#note-11
# This translation needs proofreading. The latest translation is here:
#   https://gist.github.com/b2c4f223d3ee0bca72ad#file_3.txt
#####

Sorry for that I don't join to this discussion because of busy.

I think the following issues for release ruby 1.8.8 from current ruby 1.8.8dev.

1. Make 1.8 implementation MRI only

    People shouldn't need supporting 1.8 othar than MRI.
    But in actuality, JRuby is continuing to support 1.8, and JRuby community
    doesn't think well for 1.8.8.

    If we'll release 1.8.8, we doesn't require supporting 1.8.8 to other
    implementations, and I thought that start working at 1.8.8 after other ruby
    implementations finish supporting 1.8(.7). But I'm disappointed because I 
    heard that JRuby's 1.9 supporting level is not completed yet,and I thought
    that stop discussion about 1.8.8 until the background moves. (Froze we
    release 1.8.8 or not.)

    Matters of that someone needs MRI 1.8 are already raised, I don't add more.
    But if we'll release 1.8.8, that is for peoples who needs 1.8.8, so
    any opinions like "Don't need" don't effect to releasing.

    But, we mustn't occur problems by releasing 1.8.8. Like users which using
    1.8.8 post project which already migrated to 1.9 an opinion about
    corresponding to 1.8.8. To avoid this, we have to take a clear the following
    issues, and make those for causes.

2. Implement features for compatibility with ruby1.9.2

    * 1.9.2+ compatibility warnings; like occur by default.
    * Occur warning when Block variable name and Local variable name are equal
    * magic comment; occur warning when doesn't equal with $KCODE
    * Splat syntax (like [a, *b, c] ) when not tail of list.
    * ->(args){...} #=> Proc syntax

    (Raise more if have more features)

3. Test compatibility with ruby 1.8.7

    * Test left and right with RubySpec, 3rd-party gems, in-house apps
    * Report for bug if code works well at 1.8.7, but doesn't work at 1.8.8

      Some inadequacy compatibility codes and some forceful monkey patches
      don't work well, but we supports fixing them.

Many time needs for working with the above issues, so we need manpower with
avidity. If we can't take it, same as current, so 1.8 users use 1.8.7,
or 1.8 users which have different needing use 1.8.8dev and maintain 1.8.8dev
by voluntary developers.

... It is essence of my thinking.

Thanks.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4239

----------------------------------------
http://redmine.ruby-lang.org