forked from TracksApp/tracks
-
Notifications
You must be signed in to change notification settings - Fork 0
Releasing tracks
bsag edited this page Jul 16, 2011
·
1 revision
These steps are for maintainers with git commit access
Create maintenance branch for release. For example for release 2.0
git checkout -b -r 2.0_branch
Assuming
- Documentation was updated in master
- /README
- /doc/CHANGELOG
- README_DEVELOPERS
- Manual was updated on branch gh-pages
- default databases are current, i.e. migrated and VACUUMed by
sqlite db/tracks-20-blank.db
vi config/database.yml —> change development db to sqlite db/tracks-20-blank.db
rake db:migrate
sqlite3 db/tracks-20-blank.db
vacuum;
.exit
repeat for tracks-20-example.db and tracks-20-test.db
- update version numbers and check copyright dates in
- README
- /doc/CHANGELOG
- /config/environment.rb and comment out the git date
- create release tag
git tag v2.0RC2
git push —tags
tbd