Version 2.3.rc1

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.3devel
+* Version: 2.3.rc1
 
 [![Build Status](https://travis-ci.org/TracksApp/tracks.svg?branch=2.3_branch)](https://travis-ci.org/TracksApp/tracks)
 

config/initializers/tracks.rb

@@ -1,7 +1,7 @@
-tracks_version='2.3devel'
+tracks_version='2.3.rc1'
 # 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`
-tracks_version=tracks_version + ' ('+info+')'
+#info=`git log --pretty=format:"%ai" -1`
+#tracks_version=tracks_version + ' ('+info+')'
 
 TRACKS_VERSION=tracks_version

doc/CHANGELOG.md

@@ -1,4 +1,4 @@
-## Version 2.3devel
+## Version 2.3
 
 ### New and changed features
 * Numerous bug fixes

doc/upgrading.md

@@ -1,18 +1,16 @@
 # Upgrading Tracks
 
-## Upgrading from Tracks 2.2 to 2.3devel
+## Upgrading from Tracks 2.2 to 2.3
 
-WARNING: 2.3devel is a development tree of Tracks and may (will?) contain bugs that might destroy your data! It is not recommended to upgrade to 2.3devel unless you know what you are doing.
-
-That said. To upgrade:
+To upgrade:
 
 1. Back up your existing database and installation of Tracks
-2. Install Tracks 2.3devel in a new directory. Or you can create a separate installation of 2.3 for testing purposes.
-3. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3devel directory.
+2. Install Tracks 2.3 in a new directory. Or you can create a separate installation of 2.3 for testing purposes.
+3. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3 directory.
 4. 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.
 5. 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!
 6. Precompile your static assets (css, javascript, etc.) by running `bundle exec rake assets:precompile RAILS_ENV=production`.
-7. Run `bundle exec rails server -e production` inside your Tracks 2.3devel directory to start up Tracks. Or use `-e development` if you intend to try your changes and get more log info.
+7. Run `bundle exec rails server -e production` inside your Tracks 2.3 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 use Tracks with the built in webserver called WEBrick for production, you’ll need to change `config.serve_static_assets` to `true` in `config/environments/production.rb` in order for the images, stylesheets, and javascript files to be served correctly.