From owner-freebsd-ruby@freebsd.org  Fri Jan 22 10:15:05 2016
Return-Path: <owner-freebsd-ruby@freebsd.org>
Delivered-To: freebsd-ruby@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E8E9A8CFE3
 for <freebsd-ruby@mailman.ysv.freebsd.org>;
 Fri, 22 Jan 2016 10:15:05 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 7EC761159
 for <freebsd-ruby@freebsd.org>; Fri, 22 Jan 2016 10:15:05 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 7B86AA8CFE2; Fri, 22 Jan 2016 10:15:05 +0000 (UTC)
Delivered-To: ruby@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B220A8CFE1
 for <ruby@mailman.ysv.freebsd.org>; Fri, 22 Jan 2016 10:15:05 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: from toco-domains.de (mail.toco-domains.de
 [IPv6:2a01:4f8:150:50a5::6])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4ADE51158;
 Fri, 22 Jan 2016 10:15:05 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6])
 by toco-domains.de (Postfix) with ESMTPA id 1DF171B22064;
 Fri, 22 Jan 2016 11:15:03 +0100 (CET)
Subject: Re: Obsoleting Rails 3.x?
To: Steve Wills <swills@FreeBSD.org>, ruby@freebsd.org
References: <56A08842.8090105@toco-domains.de> <56A10C9A.3090604@FreeBSD.org>
From: Torsten Zuehlsdorff <mailinglists@toco-domains.de>
Message-ID: <56A20126.9040901@toco-domains.de>
Date: Fri, 22 Jan 2016 11:15:02 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <56A10C9A.3090604@FreeBSD.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ruby>,
 <mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby/>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
 <mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 10:15:05 -0000

On 21.01.2016 17:51, Steve Wills wrote:

>> while working on many ports i figured out there are a bunch of
>> dependencies to our Rails 3 port. But for many rubygems this is not
>> needed - they already work with Rails 4.2. Often this results in a port
>> based on Rails 3 and a slave port with Rails 4.2.
>> This will become even more bad because Rails 5 is already on its way.
>>
>> Also when i'm understanding the release notices correct (i found them
>> quite confusing) they state:
>> - Rails 3.2 will only fix really bad security issues (while letting
>> "normal" security issues intact)
>> - you seem to get the fixes just if you pay
>>
>> So i would announce, that we go through the gems and do a little
>> cleanup. If a gem will work with Rails 4.2 we should switch its
>> dependency to this version instead of Rails 3.
>>
>> Your thoughts? Objections?
>
> Sounds good, let's do it.

Fine! :) I will start next week!

Greetings,
Torsten