Bonjour à tous.
Rails 2.3.5 est annoncé sur Twitter, mais je n'ai pas trouvé de CHANGELOG ou de post de blog détaillant les modifs.
Tristesse.

Heureusement, on peut extraire quelques infos utiles du Lighthouse, en prenant la liste des bugs résolus.
La voici. En Résumé, plein de corrections bienvenues sur le modèle, le fameux patch de sécurité (vulnérabilité XSS sur TextHelper::truncate), de la compatibilité Ruby 1.9...

En attendant le sacro-saint post d'annonce.

MYSQL
the default, preferred table collation for MySQL has been changed. Previously, Rails defaulted to utf8_general_ci when either the database or the table creation script did not dictate otherwise. Now, that has been changed to utf8_unicode_ci. Certainly worth a note with so many Rails applications using MySQL in their back-end.

WONTFIX
#routes_for method doesn't work at all

RUBY 1.9
Ruby 1.9 compat: fix script/generate with -g option
Ruby 1.9 compat: plugin/install git://... always fails in Ruby 1.9
Ruby 1.9 compat: fix script/generate with -c option

BIBLIOTHEQUES
"bös".chars.reverse is "s̈ob" for decomposed string
LibXML XmlMini parser does not handle cdata
Nokogiri XmlMini code is broken on 2-3-stable
nested resource routes not generated correctly

REQUÊTES & ROUTAGE
polymorphic_url should allow a symbol in place of a record
Internet Explorer Accept header
First request will always have an empty body due to delayed load of action_controller/cgi_process

TESTS
Some assertions for the testing of ActionView::TestCase are worthless
ActionView::TestCase dies when rendering a layout

VUE
Allow explicit placement of hidden fields with nested models (actionview, fields_for, nested_attributes_for)
Accept arrays for nested attributes (fields_for, action_view, nested_attributes_for)
number_to_human_size fails for some values

MODELE
Explicit autosave => false should override new_record
AutosaveAssociation should not validate associated model if marked_for_destruction
ActiveRecord::Error does not allow values to add errors
avoid calling #valid? on destroyed associated records
has_one with :foreign_key & :primary_key
Ensure AR validation errors to be ordered in declared order
Association :dependent => delete_all + :foreign_key can result in data corruption
Validation of autosaved associations is broken
autosave for has_one does not work properly with primary_key option
Rename _delete to _destroy in nested attributes
accepts_nested_attributes_for raises NoMethodError when saving polymorphic belongs_to
autosave associations should not destroy twice when saving twice