From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from juno.localdomain ([141.84.9.6]) by mx.google.com with ESMTPS id p15sm1507508fae.11.2011.09.08.12.50.10 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Sep 2011 12:50:10 -0700 (PDT) Received: by juno.localdomain (Postfix, from userid 1000) id 6568781C85; Thu, 8 Sep 2011 21:50:09 +0200 (CEST) From: Christian Neukirchen To: rack-core@googlegroups.com Cc: rack-devel@googlegroups.com Subject: Re: 1.1 Roadmap / EOL References: <787C9DA2-5CBC-43A3-B9FA-A984A3689DA7@gmail.com> Date: Thu, 08 Sep 2011 21:50:09 +0200 In-Reply-To: <787C9DA2-5CBC-43A3-B9FA-A984A3689DA7@gmail.com> (James Tucker's message of "Thu, 8 Sep 2011 12:33:55 -0700") Message-ID: <87zkie3jbi.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii James Tucker writes: > Hi all, > > I really want to EOL 1.1. There are some patches I'm bringing in for > the (late - sorry) security releases, and to get Rails 2.x cookie > issues sorted. > > I want to attach a provisional EOL statement to the README in the > 1.1.3 release. Rails is also gearing up to EOL the 2.x series. +1 > I would STRONGLY (in the most vehement definition) recommend upgrading > your apps to rails > 2 and rack > 1.1 regardless of the outcome of any > further discussions. +1 :) -- Christian Neukirchen http://chneukirchen.org