Re:Upgrading GitHub to Rails 3 with Zero Downtime
by holman on Monday September 15, 2014 @11:04PM
(#8322826)
We already have the app booting on 3.2; the goal is to try to get to 4.0 and track master fairly quickly. No one's eager to have to go through this whole process again in a year. ;)
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by InAnEmergency on Tuesday September 16, 2014 @03:11AM
(#8323390)
Rails 3 is already only receiving security updates for "severe" issues, see http://rubyonrails.org/security/
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by jrochkind1 on Tuesday September 16, 2014 @07:31AM
(#8323951)
thanks for that link!
While it says `/security`, it's actually the only link I know of with an updated list of how the maintenance policy applies to current versions.
I hadn't been able to find such before, only dated news/blog announcements, which can get out of date really quickly as fast as Rails goes.
But I understand why they did it. And I sympathize. The Rails treadmill is a harsh regime.
I wonder if they're considering what the heck they are going to do when Rails 5 comes out (target: spring/summer of 2015. Less than 12 months) and Rails 3.x stops even receiving security updates. I mean, clearly they have the resources to backport security updates themselves that's not a problem -- it's just that they're still not quite in 'the modern world', they've just kept from falling even further behind.