On August 26, 2019, the GitHub application was deployed to production with 100% of traffic on the newest Rails version: 6.0. Read more about our process for upgrading, what we learned, and what’s next.
Overview
The article discusses GitHub's successful deployment of Rails 6.0, highlighting the significant contributions made by GitHub engineers and the smooth upgrade process. It emphasizes the benefits of staying current with framework updates, including improved performance, security, and community contributions.
What You'll Learn
How to effectively upgrade a Rails application to a new version without impacting production
Why contributing to open source frameworks like Rails enhances both internal and community development
How to implement a weekly upgrade process to catch regressions early in the development cycle
Key Questions Answered
What was the impact of upgrading GitHub to Rails 6.0?
How did GitHub contribute to the Rails 6.0 release?
What process did GitHub use to upgrade to Rails 6.0?
What are the benefits of staying current with the Rails framework?
Key Statistics & Figures
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Key Actionable Insights
1Implement a weekly upgrade process for your Rails applications to catch regressions early.This proactive approach allows developers to identify issues shortly after they are introduced, making it easier to maintain application stability and performance.
2Encourage your engineering team to contribute to open source projects like Rails.Contributing not only improves the framework but also enhances your team's skills and fosters a sense of community, leading to better collaboration and innovation.
3Prioritize involvement in major framework releases to ensure stability during upgrades.By being actively engaged in the development of the framework, your team can anticipate changes and prepare your application accordingly, minimizing disruptions during upgrades.