I've now pushed commits to mainline:next that upgrades our Rails version:

- Unvendor Rails (i.e. rm -fr vendor/rails, configure Rails in Gemfile)
- Upgrade from 2.3.5 to 2.3.14

This means we're no longer on a completely ancient version of Rails. There
has been
some non-trivial changes in Rails between the two versions, so please
report if you
find any oddities. The two main things to look out for are:

1) Strangely translated text (I made quite a few changes to how our
internationalization
    was implemented, to accommodate newer versions of I18N)
2) Over-eager HTML escaping. Will likely manifest as "broken UI". Our tests
does not
    cover the HTML generation very exhaustingly, but I've surfed through
quite a bit, and
    it looks OK to me.

Please beware that the next branch with this change is on the risky side.
We'll be using
it on our internal setup for a little while before merging to master and
deploying on
gitorious.org. If you have setups that can take a visual bug or two, please
try it out and
help us find bugs.

How does this upgrade help us?

1) Lots and lots of bug fixes from the Rails team, including security
patches
2) Tackled some deprecated APIs and flat out failing things that will help
us move
    on to Rails 3
3) Solves a dependency deadlock involving Rack, that has made my integrating
    the new code browser, uhm, challenging
4) Solves the problem of "your rubygems is to new, please downgrade"

For end users the upgrade is unlikely to bring any visual changes.

-- 
MVH
Christian

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Reply via email to