Date: Fri, 22 Jan 2016 11:15:02 +0100 From: Torsten Zuehlsdorff <mailinglists@toco-domains.de> To: Steve Wills <swills@FreeBSD.org>, ruby@freebsd.org Subject: Re: Obsoleting Rails 3.x? Message-ID: <56A20126.9040901@toco-domains.de> In-Reply-To: <56A10C9A.3090604@FreeBSD.org> References: <56A08842.8090105@toco-domains.de> <56A10C9A.3090604@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56A20126.9040901>