I upgraded to rails 2.3 I had already upgraded passenger before I
deployed my app.
The passenger upgrade went without a hitch. The rails upgrade required
a lot of code changes and upgrading a lot of plugins.
If you have gone through the trouble of upgrading rails I'd suggest
you upgrade passenger. It only takes a few seconds.
I'm a bit out of touch with Rails at the mo…
> Well, it seems serious enough to warrant a double upgrade, but I am
> not sure if the bug applies only if one uses Rack or it basically
> applies to all??
Rails includes Rack these days doesn't it.
From 2.3 on, Rails uses Rack as the glue between Rails and the
webserver, so yes you will be using it.
You should upgrade Passenger when you upgrade to 2.3, because 2.3.3 at
least contains an updated version of Rack that is not fully compatible
with early versions of Passenger.
You should be able to upgrade Passenger while still on 2.2 if you're
nervous about upgrading both at the same time, but we tried out latest
REE + current Passenger + Rails 2.3.3 on a staging server on thursday
and it tested out fine (no errors under load test etc.).