Hey readers! This is Kasper bringing you the latest news in Rails. I’m writing from deep winter-like Copenhagen, starting on the last month of the decade.
Speaking of progress, Rails recently crossed 75.000 commits on GitHub. Last time we marked commit progress was over 4 years ago for 50.000. I happened to write that issue too, you can read it here.
As always, this release is loaded with fixes and improvements. It’s currently set to ship Monday Dec 2 and so far no regressions have been found as far as I know. Final day to test the release candidate on your app, try it out ✌️
The final bug fix release of Rails 5.2, now it’ll only get security releases from here on out. Good time to plan a Rails 6 upgrade.
For the most part we highlight particular interesting commits in this newsletter, but there’s usually other stuff we don’t get to. Stuff that could help you make sense of Rails itself. This week I’d like to try to remedy that.
Here’s all changes since last time. Visit the link and each time you see “Merge pull request #12345”, click ‘em. Feel free to see Files Changes and on particularly interesting files, you can try “View File” and read some surrounding code. This can be overwhelming so go easy. But that’s pretty much a fine way to start reading Rails’ actual code. It’s all Ruby all the way down.
Now, some of the people in the list are on certain Rails teams. You’ll likely interact with some of them if you submit a pull request. Here’s who’s in the current change list, but not the full teams.
carlosantoniodasilva, eileencodes, georgeclaghorn, kaspth (that’s me), rafaelfranca are on Rails Core. gmcgibbon, jhawthorn, kamipo and y-yagi have commit access. Meanwhile eugeneius and vipulnsward are on the issues team, so they can triage issues and merge documentation PRs.
That’s it for now, hope it’s useful 🙌
Also 41 people contributed since last time including several first time contributors.
Hope you dig it. See ya next time! 👋🏻