Skip to content

How to Release

Reid Burke edited this page May 23, 2013 · 1 revision

Hooray, it's time to ship! Here's what to do.

Prerequisites

  • Node.js, of course.
  • Fabric and a .hosts.json from Reid.

Make the version commit

  1. Update package.json.
  2. Update HISTORY.md.
  3. Update doc/yeti/project.json.
  4. Commit all this with Version X.Y.Z. as the message.

Remove untracked files

Run git clean -nd and move anything you need elsewhere. If you want to keep untracked files, now is a good time to clone your current directory to a new directory.

Make the website

We need dev dependencies so we can run code coverage during make site.

npm install
./jake dep
make clean
make site

Do the release

We need to get rid of the dev dependencies first, then release the completed site, tag and push the tag, and push to npm.

Warning: This will delete untracked files. Make sure you know what will be removed with git clean -nd first.

make release-dep
fab release

Push to master

If the release is truly good, push to master.

git push all master

Reset your dev environment

Go back to un-minified JS.

./jake dep

Bump version for pre-release

Same as before, but increment Z and add pre at the end.

  1. Update package.json.
  2. Update HISTORY.md.
  3. Update doc/yeti/project.json.
  4. Commit all this with Version X.Y.Zpre. as the message.