diff --git a/README.md b/README.md
index d78b730ec..c9c45f162 100644
--- a/README.md
+++ b/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.3.rc1
+* Version: 2.3.0
 
 [![Build Status](https://travis-ci.org/TracksApp/tracks.svg?branch=2.3_branch)](https://travis-ci.org/TracksApp/tracks)
 
diff --git a/config/initializers/tracks.rb b/config/initializers/tracks.rb
index cb13c93af..aa6925a8b 100644
--- a/config/initializers/tracks.rb
+++ b/config/initializers/tracks.rb
@@ -1,4 +1,4 @@
-tracks_version='2.3.rc1'
+tracks_version='2.3.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`
diff --git a/doc/CHANGELOG.md b/doc/CHANGELOG.md
index 927d06cc2..aaaaa9815 100644
--- a/doc/CHANGELOG.md
+++ b/doc/CHANGELOG.md
@@ -1,4 +1,4 @@
-## Version 2.3
+## Version 2.3.0
 
 ### New and changed features
 * Numerous bug fixes
diff --git a/doc/upgrading.md b/doc/upgrading.md
index 21dd89b46..ecd86e0c3 100644
--- a/doc/upgrading.md
+++ b/doc/upgrading.md
@@ -1,16 +1,16 @@
 # Upgrading Tracks
 
-## Upgrading from Tracks 2.2 to 2.3
+## Upgrading from Tracks 2.2.x to 2.3.0
 
 To upgrade:
 
 1. Back up your existing database and installation of Tracks
-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.
+2. Install Tracks 2.3.0 in a new directory. Or you can create a separate installation of 2.3.0 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.0 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.3 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.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 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.