Merge pull request #2292 from TracksApp/release-2.4

Version 2.4.0

README.md

@@ -9,7 +9,7 @@
 * IRC channel: #tracks on Freenode
 * Original developer: bsag (http://www.rousette.org.uk/)
 * Contributors: https://github.com/TracksApp/tracks/wiki/Contributors
-* Version: 2.4devel
+* Version: 2.4.0
 
 [![Build Status](https://travis-ci.org/TracksApp/tracks.svg?branch=master)](https://travis-ci.org/TracksApp/tracks)
 [![Code Climate](https://codeclimate.com/github/TracksApp/tracks/badges/gpa.svg)](https://codeclimate.com/github/TracksApp/tracks)

config/initializers/tracks.rb

@@ -1,4 +1,4 @@
-tracks_version='2.4devel'
+tracks_version='2.4.0'
 # comment out next two lines if you do not want (or can not) the date of the
 # last git commit in the footer
 info=`git log --pretty=format:"%ai" -1`

doc/CHANGELOG.md

@@ -1,4 +1,5 @@
-## Version 2.4
+## Version 2.4.0
+
 ### New features
 * Removed support for deprecated password-hashing algorithm. This
   eliminates config.salt. Note the addition of a pre-upgrade step to
@@ -9,9 +10,9 @@
 * All REST APIs now also accept user token as password.
 * The stats view now uses Charts.js instead of the Flash-based chart library.
 * A Docker environment is used unless the .skip-docker file exists.
-* Rails 4.2
+* Rails 5.2
 * Thin replaces WEBrick as the included web server
-* Tracks is tested on Ruby 1.9.3, 2.0.0, 2.1, and 2.2.
+* Tracks is tested on Ruby 2.4 and 2.5
 * The MessageGateway will save the received email as an attachement to the todo
 * Add a configuration option for serving static assets from Rails
 

doc/upgrading.md

@@ -1,19 +1,19 @@
 # Upgrading Tracks
 
-## Upgrading from Tracks 2.3 to 2.4devel
+## Upgrading from Tracks 2.3 to 2.4.0
 
-WARNING: 2.4devel is a development tree of Tracks and may (will?) contain bugs that might destroy your data! It is not recommended to upgrade to 2.4devel unless you know what you are doing.
+These upgrade instructions are rough. Please suggest improvements in a GitHub issue if you run into problems.
 
-That said. To upgrade:
+To upgrade:
 
 1. Support for Tracks' older, less secure password-hashing algorithm has been removed. Active user accounts will already have been upgraded, but you should check for outdated accounts by running `bundle exec rake tracks:check_passwords` from your existing Tracks install directory. If any users are listed, they can log in to be prompted to update their passwords, or you can run `bundle exec rake tracks:password USER=<username>` to reset their passwords using the new algorithm. If no users are listed, you can proceed with the upgrade.
 2. Back up your existing database and installation of Tracks
-3. Install Tracks 2.4devel in a new directory. Or you can create a separate installation of 2.4devel for testing purposes.
-4. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.4devel directory.
+3. Install Tracks 2.4.0 in a new directory. Or you can create a separate installation of 2.4.0 for testing purposes.
+4. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.4.0 directory.
 5. Check that you have all dependencies installed: `bundle install --without development test` Or leave out the `--without development test` part if you intend to test or develop on this tree.
 6. 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!
 7. Precompile your static assets (css, javascript, etc.) by running `bundle exec rake assets:precompile RAILS_ENV=production`.
-8. Run `bundle exec rails server -e production` inside your Tracks 2.4devel directory to start up Tracks. Or use `-e development` if you intend to try your changes and get more log info.
+8. Run `bundle exec rails server -e production` inside your Tracks 2.4.0 directory to start up Tracks. Or use `-e development` if you intend to try your changes and get more log info.
 
 Please note that if you intend to deploy Tracks using its included web server, you’ll need to copy over the `serve_static_assets` option into your `config/site.yml` and set it as it was in `config/production.rb` in order for the images, stylesheets, and javascript files to be served correctly.