This week in Rails: RC releases, summer opportunities, turbo partials and more!

Hi all! o/

Here is Washington bringing you this week’s news from our favorite framework. I hope you have made it to Friday the 13th without any major hiccups (I can’t say the same about my internet provider). Either way, it’s time to grab a drink, wind down and read on!

4.2.1.rc4 and 4.1.10.rc4 have been released

Give them a try on your projects to help make the next release as rock solid as possible. Many regressions have already been fixed and the final release should be out on March 17.

This week’s Rails contributors

Couple more developers made their first commit into Rails this week. Take a moment to review the open issues, perhaps you will find something related to your day job, manage to fix it and have your first patch in Rails!

Summer Opportunities

Google Summer of Code 2015

It’s that time of the year again! As reported last week, we have been selected to participate in this year’s Google Summer of Code program. This week, a few more exciting ideas have landed on our project page!

Applications will open next week, so please help spread the word!

Rails Girls Summer of Code

Speaking of summer, Rails Girls Summer of Code have just opened their applications today. If your company can afford it, consider becoming a sponsor!

New Stuff

Mostly inspired by shopify/turbograft turbolinks now also supports partial replacement. Checkout the PR with docs as well for usage details.

Improved

All Rails tests run in random order

As of this week Rails is giving another try on running tests in random order!!! You should probably try the same on all your projects for more reliable test results.

Fixed

Rails 5 will need Ruby 2.2.1 or higher

Apparently Ruby 2.2.0 kwargs were still not that stable. A related issue caused a segfault error on ActionPack tests. So Rails 5 will require at least Ruby 2.2.1.

Fix rollback of frozen records

In case your project upgrade to Rails 4.2.0 raised any Can’t modify frozen hash errors, checkout the latest release candidate. Chances are it will be fixed in Rails 4.2.1.

Wrapping up

That’s all for This week in Rails. As always, there are more changes than we have room to cover here, but feel free to check them out yourself!

P.S. If you enjoyed this newsletter, why not share it with your friends? :) If you wish to be part of this project please don’t hesitate to contact Godfrey – there’re a lot of ways you could help make this newsletter more awesome!