Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-09-21 21:40:48 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Bump version to 2.4devel

Browse source
This commit is contained in:
Dan Rice 2014-10-02 12:02:01 -04:00
parent 9b901d2d93
commit 7556db7529
4 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -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.4devel
[![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)

2
config/initializers/tracks.rb
View file

@ -1,4 +1,4 @@
tracks_version='2.3devel'
tracks_version='2.4devel'
# 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`

4
doc/CHANGELOG.md
View file

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

14
doc/upgrading.md
View file

@ -1,23 +1,21 @@
# Upgrading Tracks
## Upgrading from Tracks 2.2 to 2.3devel
## Upgrading from Tracks 2.3 to 2.4devel
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.
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.
That said. 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.4devel in a new directory. Or you can create a separate installation of 2.4devel 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.4devel 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.4devel 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.
The Czech locale has been renamed from `cz` to `cs` in accordance with ISO standards. Users of the Czech locale will need to edit their preferences and reselect the locale under the new name.
## Upgrading from older versions of Tracks
Upgrade to Tracks 2.2.3 first. Follow the upgrade instructions included in Tracks 2.2.3.
Upgrade to Tracks 2.3 first. Follow the upgrade instructions included in Tracks 2.3.