update installation manual for 2.2

doc/installation.textile

@@ -42,7 +42,7 @@ h3.  What you need to install
 
 If you don't want to (or can't) use one of the all in one installations, you'll need to install a few things, depending on your platform and your needs.
 
-# *Ruby*. Tracks requires either Ruby 1.8.7 or Ruby 1.9.x. Ruby 1.9.x is the recommended version.
+# *Ruby*. Tracks requires either Ruby 1.8.7 or Ruby 1.9.x. Ruby 1.9.x is the recommended version. Please note that support for ruby 1.8.7 will be dropped after this release!
 # *RubyGems*. Tracks was tested on version 1.8.24. You may upgrade using @gem update --system@. The gems needed by Rails to interact with the database have to be compiled on the platform on which they will be run, so we cannot include them with the Tracks package, unlike some other gems. So you will need to "download":http://rubyforge.org/frs/?group_id=126 and install RubyGems (run @ruby setup.rb@ after extracting the package). If you use Linux, rubygems may be available throught your packaging system. Mac OS X users already have RubyGems and the SQLite3 gem already installed on their systems. Once installed you can use RubyGems to install the gems you need for your database. Run @bundle install --without development test@ from the directory you installed Tracks in. This will install all needed gems, including those for MySQL and Sqlite3. If you do not want one of them, you can comment it out in your @Gemfile@ which can be found in the root of the Tracks installation.
 # *Database*. The easiest option is to use SQLite3, as the database is included in the package. You may need to install it first for your platform (see "sqlite.org":http://sqlite.org/download.html for downloads and installation instructions). If you want to use MySQL, download and install a package for your platform from "MySQL.com":http://dev.mysql.com/downloads/mysql/5.0.html. The basic steps for Postgresql should be similar to those for MySQL, but they will not be discussed further here.
 

doc/upgrading.textile

@@ -1,5 +1,23 @@
 h1.  Upgrading Tracks
 
+h2. Upgrading from Tracks 2.1.x or 2.2RC to 2.2
+
+This release adds a variety of new features and bugfixes to Tracks.
+
+The database will need to be migrated as part of the install. 
+
+To upgrade:
+# Back up your existing database and installation of Tracks
+# Install Tracks 2.2 in a new directory
+# Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.2 directory.
+# Check that you have all dependencies installed: @bundle install --without development test@
+# Run @bundle exec rake db:migrate RAILS_ENV=production@ to update your old database to the new schema. This is the point of no return. Make sure you have backups!
+# The administrator email address shown on the signup page is now configured in @config/site.yml@. Edit your @config/site.yml@ and add an @admin_email@ option. See @config/site.yml.tmpl@ for an example.
+# If you're using mysql, change the database adapter from @mysql@ to @mysql2@ in your @config/database.yml@ file. The @mysql2@ adapter replaces the @mysql@ adapter in Rails 3.2
+# Precompile your static assets (css, javascript, etc.) by running @bundle exec rake assets:precompile@.
+# Run @bundle exec rails server -e production@ inside your Tracks 2.2 directory to start up Tracks 2.2.
+# Once you are happy that everything is working well, delete your old Tracks directory.
+
 h3. Upgrading from Tracks 2.1, 2.1.1, 2.1.2, 2.1.3 to 2.1.4
 
 The purpose of this release is to address several security vulnerabilities that were recently discovered in Rails. For details about the contents of the release, please see the "difference view":https://github.com/TracksApp/tracks/compare/v2.1.1...v2.1.4 on GitHub.