addressalign-toparrow-leftarrow-leftarrow-right-10x10arrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1languagelaunch-new-window--smalllight-bulblightning-boltlinklocation-pinlockm-swarmSearchmailmediummessagesminusmobilemoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstar-shapestartickettrashtriangle-downtriangle-uptwitteruserwarningyahooyoutube

Want to give back to open source? Come help make Rails 4.1 the smoothest upgrade ever!

From: Godfrey C.
Sent on: Friday, November 29, 2013, 1:47 AM
Hello team VanRuby!

Are you working on a Rails 4 app? Want to give back to open source? Here's your chance!

Rails 4.1 is just around the corner (if you are curious, I'm preparing a "What's new in Rails 4.1" lightning talk for our next meetup). As you might remember from the past, upgrading Rails used to be a painful process. Thanks to the new release policy Rails implemented during the 3.2 -> 4.0 transition, upgrading has become a lot easier.

Still though, with a codebase as large as Rails', unintentional breaking changes can still sneak in from time to time. Adding to that, sometimes third-party gems might depend on Rails' internal APIs, causing them to stop working with major upgrades. Realistically, there is only so much the core team can only do to without people testing in the wild and providing feedback on what's broken.

That's where we can help! This coming Tuesday we will be running a special "upgrade clinic" at our hacknight (and probably the next few hacknights too). To participate, bring a working Rails 4 app with you, ideally a production apps* with good test coverage. Together, we'll try to upgrade it to Rails master and see what breaks. Then, we'll guide you through the process on how to triage problems and submit helpful bug reports with reproducible test cases. We can also help improve the upgrade guides, and "seed" stackoverflow with answers for specific problems you encountered along the way. As a team, we can work together and help make Rails 4.1 the smoothest upgrade ever!

Looking forward to seeing you on Tuesday! Bring an app!

Godfrey

* You can even bring your app from work! You won't have to commit/deploy the upgraded version, but by testing the process and discover problems early on, you will also be doing your team a huge favour!

People in this
group are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy