Hello everyone! I hope you're having an AMAZING Monday. If you Monday
wasn't AMAZING enough already, I've decided to make it even better by releasing
Rails version 3.0.7!
(As a side note, sometimes I have a hard time telling if my day is
AMAZING or FABULOUS. If anyone has hints, let me know!)
I want to say thanks to Santiago for handling the release candidate gems. He's
on vacation, so I get to do the real thing.
The main change in this release is to fix a performance regression in
ActiveRecord that was introduced in version 3.0.6.
For those that want the TL;DR of the commits, here are the pertinant CHANGELOG
entries for each project:
## activesupport
* `Hash.from_xml` no longer loses attributes on tags containing only whitespace
[André Arko]
## activerecord
* Destroying records via nested attributes works independent of `reject_if`
LH #6006 [Durran Jordan]
* Delegate any? and many? to Model.scoped for consistency [Andrew White]
* Quote the ORDER BY clause in batched finds - fixes #6620 [Andrew White]
* Change exists? so records are not instantiated - fixes #6127. This prevents
`after_find` and `after_initialize` callbacks being triggered when checking
for record existence.
[Andrew White]
* Fix performance bug with attribute accessors which only occurred on
Ruby 1.8.7, and ensure we cache type-casted values when the column returned
from the db contains non-standard chars.
[Jon Leighton]
* Fix a performance regression introduced here
86acbf1cc050c8fa8c74a10c735e467fb6fd7df8
related to `read_attribute` method [Stian Grytøyr]
## actionmailer
* remove AM delegating `register_observer` and `register_interceptor` to Mail
[Josh Kalderimis]
Great! I’m updating the gems… So if i’ve done a project using rails 3.0.6 and now i’m updating gems to rails 3.0.7, what I’ve to do inside my project? Should I change the Gem file inside my project, from rails 3.0.6 to rails 3.0.7? or run “bundle install” ? or something else?
…and another question I’ve noticed running gem list that on my system I’ve both rails 3.0.6 and 3.0.7, and the same for activerecord, activesupport, etc etc…
Is there a problem? is there a way to clean up older versions?
Great! I’m updating the gems… So if i’ve done a project using rails 3.0.6 and now i’m updating gems to rails 3.0.7, what I’ve to do inside my project? Should I change the Gem file inside my project, from rails 3.0.6 to rails 3.0.7? or run “bundle install” ? or something else?
Hi, I would recommend doing the following
adding/updating the rails line within Gemfile to look like the following:
gem ‘rails’, ‘3.0.7’
Then run ‘bundle’ from the command line within the root of your Rails project.
…and another question I’ve noticed running gem list that on my system I’ve both rails 3.0.6 and 3.0.7, and the same for activerecord, activesupport, etc etc…
Is there a problem? is there a way to clean up older versions?
This isn’t an issue and this is by design. The Gemfile will tell indicate what version you would like to use for your Rails project. Now, if you would like to use the latest of all gems, you can do the following to clean up your gems:
gem clean
However, you should be aware that other gems may depend on an earlier version of a gem(s). Thus, I would recommend not doing the above unless you truly understand all your gems and their associated dependencies.
Ok i’ve changed the Gem file from “rails 3.0.6” to “rails 3.0.7”, then run “gem clean”: it deleted all the older version.
Then I’ve finally run “bundle”, and it downloaded some older version gem, for example “mail 2.1.16” (so I’ve both mail 2.1.17 and 2.1.16). I think that’s not an issue, since my app is working perfectly…
Please reply if you have some other ideas of what’s the best when a new rails version is released.
I’ve noticed running gem list that on my system I’ve both rails 3.0.6 and 3.0.7, and the same for activerecord, activesupport, etc etc…