01 Apr '13, 10am

#sendagayarb 今日はこれを読んでいる

The best way to be sure that your application still works after upgrading is to have good test coverage before you start the process. If you don't have automated tests that exercise the bulk of your application, you'll need to spend time manually exercising all the parts that have changed. In the case of a Rails upgrade, that will mean every single piece of functionality in the application. Do yourself a favor and make sure your test coverage is good

Full article: http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails...

Tweets

@DanielZarick @rbates does.

railscasts.com 03 Apr '13, 3pm

In this first part of a two part series you will learn basic Backbone concepts including models, collections, routers, vie...

Double Shot #1098: Upgrade to Rails 4 – An eboo...

afreshcup.com 02 Apr '13, 1pm

is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the univer...

Boas praticas em projetos Ruby/Rails #soudev

akitaonrails.com 02 Apr '13, 3pm

Eu gosto de usar os gráficos de projetos do Github. Ele conta muito sobre os programadores envolvidos no projeto. E antes ...