By default, we do not upgrade customer's Rails applications to newer releases of Rails.  We have noticed that a large number of customers haven't been upgrading, and just want to make sure that customers know how to do so!

Simply edit your application's config/environment.rb as such to specify the version you would like to upgrade to:
-RAILS_GEM_VERSION = '1.1.6'

+RAILS_GEM_VERSION = '2.1.1'

Then, run 'rake rails:update' from with in your application's directory.


Notable upgrades for you would be:
 1.2.0
 1.2.6
 2.0.0
 2.0.4
 2.1.0
 2.1.1

Other versions can be available as well, but these are the earliest and latest point-releases available within each major release at the time of this writing.

We've had a few customers asking about why their Django admin interface is no longer working, since the upgrade to Django 1.0.

Changes in Django 1.0 required a couple changes to the url.py file in order to access the admin view.  Here is an example of how to modify the file:

# Add following lines for 1.0 compat, to top of file
from django.conf.urls.defaults import *
from django.contrib import admin
import os
admin.autodiscover()

# and then under urlpatterns, eg:
urlpatterns = patterns('',
    # Remove old entry, eg:
    # (r'^admin/', include('django.contrib.admin.urls')),
    # Add new entry, eg:
     ('^admin/(.*)', admin.site.root),

This is a quick notice that we are asking that customers hold off from upgrading GCC to version 4.3 at this time.  A problem exists in all current Linux releases (from all vendors) which renders GCC 4.3.0 and higher incompatible.  A kernel update will be provided shortly to resolve this issue.

UPDATE: all should now be okay in 2.6.26.5