Updates for the Tracks 2.2 release

[mattr-]

Updates to the site for the Tracks 2.2 release. Please review!

Warning: Do not merge until the release is ready!

[dnrce]

Thanks, Matt, that's a great first pass. And thanks for mentioning me. Aw, shucks. 😊

I've committed some small changes but it's late here so I'll note some other bigger to-dos without tackling them:

• We haven't addressed #1330 yet. Out of the box, WEBrick won't work in production mode due to the asset pipeline configuration.
• In fact, the docs don't mention asset precompilation at all yet.
• We need to make mention of bundle install --without development test for Ruby 1.8. (Maybe this should be the recommendation for all end-user installations.)
• Is the difference between mysql and mysql2 in database.yml a thing? https://groups.google.com/d/msg/tracksapp/DQEPjc7aWKE/pveUS8uFbOgJ

I'll give it another pass before we get ready to green-light the release.

[dnrce]

Let me clarify that last line: I'd like the chance to do a final edit before release, but anyone is welcome to address the above bullet points.

[lrbalt]

Great work!
I'd like to see the --without development test for production use
And we need some small instructions on upgrading from 2.2RC to 2.2 final
In the upgrade instructions we need to mention chaning mysql in database.yml to mysql2

[mattr-]

I've updated the release notes to what I think could be the final version. I don't have the energy tonight to finish this up. If someone would like to run with this some more, feel free to add more commits to this branch.

[dnrce]

Very good!

Two catches (I'm not on a PC with git at the moment but I'll get to them tomorrow):

• Asset precompilation needs to be in the install instructions as well as the upgrade instructions.
• According to the bundler docs the correct syntax is bundle install --without development test (using a space instead of a comma)

[mattr-]

Updated.

[dnrce]

Sweet.

[dnrce]

Hey, what do you guys think about moving the manual (installation and upgrading) into doc/ in the main Tracks repository? Then getontracks.org could just link to the file on GitHub. That would allow us to version the installation documentation and keep it up to date as changes are made to the working tree, while still providing good documentation for older versions of Tracks. I have this on my wishlist but why not strike while the iron's hot and do it for 2.2? If others agree with the concept I'd be happy to do the work of porting this pull request over to the main repo and creating a new pull that will replace the manual on getontracks.org with a link over to GitHub.

[lrbalt]

I'd prefer to do this for 2.3, but if you think the change doable both for tracks and getontracks repo...

[dnrce]

It's quite doable. Have a look at my merge requests and see what you think.

[dnrce]

I've merged my changes at @lrbalt's urging. Any further edits to the installation or upgrading instructions should be made inside TracksApp/tracks/doc.