<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ruby on Rails on Resolver Engineering Blog</title>
    <link>https://engineering.resolvergroup.com/tags/ruby-on-rails/</link>
    <description>Recent content in Ruby on Rails on Resolver Engineering Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © 2026 Resolver Group</copyright>
    <lastBuildDate>Wed, 29 Sep 2021 10:00:02 +0100</lastBuildDate>
    <atom:link href="https://engineering.resolvergroup.com/tags/ruby-on-rails/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrading to Rails 6.0</title>
      <link>https://engineering.resolvergroup.com/2021/09/upgrading-to-rails-6-0/</link>
      <pubDate>Wed, 29 Sep 2021 10:00:02 +0100</pubDate>
      <guid>https://engineering.resolvergroup.com/2021/09/upgrading-to-rails-6-0/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Whenever a Ruby on Rails developer hears the phrase “New Rails update!” they will no doubt experience a mixture of excitement and fear. It’s always very exciting to see the new tools that come with a new Rails version and all the new possibilities that go with it. But at the same time, you know that you are bound to have some hiccups with some legacy code or some old gem that you use on your application. Nevertheless, I decided it was time to upgrade our Rails app.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
