diff --git a/Releasing-Tracks.textile b/Releasing-Tracks.textile index fc392e2..fc2608b 100644 --- a/Releasing-Tracks.textile +++ b/Releasing-Tracks.textile @@ -1,48 +1,21 @@ -h1. Releasing Tracks - -These steps are for maintainers with git commit access - -h2. Major release - -Create maintenance branch for release. For example for release 2.0 - -
-git checkout -b 2.0_branch
-
- -Assuming - -* Documentation was updated in master -** /README -** /doc/CHANGELOG -** /doc/README_DEVELOPERS -* Manual was updated -* default databases are current, i.e. migrated and VACUUMed by -
-sqlite db/tracks-blank.sqlite3.db
-vi config/database.yml --> change development db to sqlite db/tracks-blank.sqlite3.db
-rake db:migrate
-sqlite3 db/tracks-blank.sqlite3.db
-vacuum;
-.exit
-
- -repeat for tracks-example.sqlite3.db and tracks-test.sqlite3.db - -* update version numbers and check copyright dates in -** README -** /doc/CHANGELOG -** /config/initializers/tracks.rb and comment out the git date -* push new branch to upstream -
-git push -u origin 2.0_branch
-
-* create release tag -
-git tag v2.0RC2
-git push --tags
-
- -h2. Minor release - -tbd \ No newline at end of file +h1. Releasing Tracks + +These steps are for maintainers with commit access. + +# _(Major release only)_ Make sure documentation is up to date in master. Don't change the version number yet! +** /README.md +** everything in /doc +# _(Major release only)_ Create maintenance branch for release. For example: git checkout -b 2.0_branch +# Update version numbers and check copyright dates +** /README.md +** everything in /doc +** /config/initializers/tracks.rb (comment out the git date) +# _(Major release only)_ Push new branch to upstream: git push upstream 2.0_branch +# Tag the release: +
git tag v2.0
+git push upstream --tags
+# Publicize the new release +** Post on the Tracks website +** Update the IRC topic +** Email the mailing list +** Post to Twitter \ No newline at end of file