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 (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 6F27B17C262A for ; Mon, 25 Jul 2011 14:50:35 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 9D691EA6816 for ; Mon, 25 Jul 2011 15:04:45 +0900 (JST) Received: from localhost (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 462378FC5F for ; Mon, 25 Jul 2011 15:04:46 +0900 (JST) X-Virus-Scanned: amavisd-new at funfun.nagaokaut.ac.jp Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by localhost (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Srhge1f9U8cp for ; Mon, 25 Jul 2011 15:04:46 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 246068FC5E for ; Mon, 25 Jul 2011 15:04:46 +0900 (JST) Received: from carbon.ruby-lang.org (carbon.ruby-lang.org [221.186.184.68]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 7E097952425 for ; Mon, 25 Jul 2011 15:04:43 +0900 (JST) Received: from beryllium.ruby-lang.org (beryllium.ruby-lang.org [127.0.0.1]) by carbon.ruby-lang.org (Postfix) with ESMTP id 769863C21E7BA; Mon, 25 Jul 2011 15:04:41 +0900 (JST) Received: from fluorine.ruby-lang.org (www.rubyist.net [210.251.121.216]) by carbon.ruby-lang.org (Postfix) with ESMTP id 2B7E93C21E7B9 for ; Mon, 25 Jul 2011 15:04:39 +0900 (JST) Received: from ruby-lang.org (localhost [127.0.0.1]) by fluorine.ruby-lang.org (Postfix) with ESMTP id 125B63ED32 for ; Mon, 25 Jul 2011 15:04:39 +0900 (JST) Delivered-To: ruby-core@ruby-lang.org Date: Mon, 25 Jul 2011 15:04:39 +0900 Posted: Mon, 25 Jul 2011 15:04:39 +0900 From: Yui NARUSE Reply-To: ruby-core@ruby-lang.org Subject: [ruby-core:38472] [Backport87 - Feature #4996] About 1.8.7 EOL To: ruby-core@ruby-lang.org Message-Id: References: X-ML-Name: ruby-core X-Mail-Count: 38472 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (only members can post) X-ML-Info: If you have a question, send e-mail with the body "help" (without quotes) to the address ruby-core-ctl@ruby-lang.org; help= X-Mailer: Redmine X-Spam-Checker-Version: SpamAssassin 3.1.7-deb3 (2006-10-05) on carbon.ruby-lang.org X-Spam-Level: X-Spam-Status: No, score=0.9 required=7.0 tests=BAYES_50,CONTENT_TYPE_PRESENT, FAKEDWORD_ATMARK,FORGED_RCVD_HELO,RCVD_IN_CHINA,RCVD_IN_CHINA_KR, RCVD_IN_TAIWAN,X_MAILER_PRESENT autolearn=disabled version=3.1.7-deb3 X-Redmine-Issue-Author: shyouhei X-Redmine-Issue-Id: 4996 X-Redmine-Mailinglistintegration-Message-Ids: 7874 X-Redmine-Project: ruby-187 Auto-Submitted: auto-generated X-Redmine-Site: Ruby Issue Tracking System X-Redmine-Host: redmine.ruby-lang.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Precedence: bulk List-Id: ruby-core.ruby-lang.org List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: Issue #4996 has been updated by Yui NARUSE. B Kelly wrote: > Thomas Sawyer wrote: > > @brian I basically have to concur with your sentiment. > > I've already had one issue with encoding where I simply > > could not find a solution and abandoned any effort to > > get 1.9 compatibility (gash gem). > > Was it this issue involving \0x00 vs. \000 ? > > https://github.com/judofyr/gash/issues/4 > > If so, it's not clear that this is an 'encoding' issue in > the sense that Brian refers to. As I commented to there, it's not an encoding issue. ---------------------------------------- Feature #4996: About 1.8.7 EOL http://redmine.ruby-lang.org/issues/4996 Author: Shyouhei Urabe Status: Open Priority: Normal Assignee: Category: core Target version: No, not now. Don't worry. But we have to start talking about this topic: when and how 1.8.7 should die. "You should really use 1.9". I have said this again and again and now repeat it once more. As we're about to release 1.9.3 I can't but say it is, totally wonderful. Rich features. Faster execution. Rubygems integrated. Rails works perfectly. I've been using 1.9 for years and now I can't go back to the days without it. So why there's still 1.8.7? It's also clear: for system admins. So far 1.8.7 has been adopted widely because it was a state of art ruby implementation of the day it was released. Even after you stop writing software for something, it needs bugfixes and maintenance releases. For ruby 1.8.7 , that's what I'd been offering for these three years. Now... I know many of you're still developing your software against 1.8.7 in spite of its dead-endedness. Sooner or later the whole Ruby community will move towards 1.9 and those 1.8.7-based systems are expected to become unmaintained. I don't like the situation. I want you and your system to be 1.9 ready. So to encourage your moving towards 1.9, I think I should define 1.8.7's end-of-life to be at some point in the future. I guess you're not moving to 1.9 because 1.8 is (or at least seems to be) maintained. Let's stop it. We will no longer touch 1.8.7 in any way once after the EOL. right? My current timeline (to be rescheduled) is: - Normal maintenance (as it is today): provided until June 2012, - Security fixes: provided until June 2013. Give us your opinioms. -- http://redmine.ruby-lang.org