-
Notifications
You must be signed in to change notification settings - Fork 79
How to Release
Reid Burke edited this page May 23, 2013
·
1 revision
Hooray, it's time to ship! Here's what to do.
- Node.js, of course.
-
Fabric and a
.hosts.json
from Reid.
- Update
package.json
. - Update
HISTORY.md
. - Update
doc/yeti/project.json
. - Commit all this with
Version X.Y.Z.
as the message.
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.
We need dev dependencies so we can run code coverage during make site
.
npm install
./jake dep
make clean
make site
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
If the release is truly good, push to master.
git push all master
Go back to un-minified JS.
./jake dep
Same as before, but increment Z and add pre
at the end.
- Update
package.json
. - Update
HISTORY.md
. - Update
doc/yeti/project.json
. - Commit all this with
Version X.Y.Zpre.
as the message.