contrib: publish release strategy and travis npm creds chaijs#337

.travis.yml

@@ -1,14 +1,22 @@
 language: node_js
-
 node_js:
 - 0.1
 
+script:
+- make test-travisci
+
 env:
   global:
   - secure: h4eLQ2jkR1p2O5BEyscLtbNT/84LDGFnj977SeKmg3flVTpRR+ZiYb5YvIUIYfnwsw1jlr11xv0cya23nJjJA5DQjrVS1/kg4sWrLD9Gs6TTqpSNSk0HrFpxhrHZ/uSSPfV9fbyxfDLxgq72fc55WCuY5Osy1kXmsPdJX79/cOU=
   - secure: GXrMWPVtgAG4ICawbVdzh3R+Q+tHwYT1FcgtFbn4w7s6NZUKRdDodBM0yuDZA8pxqhQvSj/HlLjkNQI4G1wPhkHESlMWzrH5737eaJ1PHQvYV/XEnpjawQXYTOg3OYEx07mHGm+mqbAaDDHulgkeI5J4NXFMQO+JG7eYTqpotXE=
   - SAUCE_CONNECT_READY_FILE=/tmp/sauce-connect-ready
   - LOGS_DIR=/tmp/chai-build/logs
 
-script:
-- make test-travisci
+deploy:
+  provider: npm
+  email: [email protected]
+  api_key:
+    secure: AgNQTECM/3Gh0q77gkrMx0jASgRh/dysPdUf7Zdsm1k9Gt+i4H99k2L8lVWqpLF1+e6lhWg9w4C08Xgz6tuOTPZZr6UzeRDl+ZjniTYK3E/tpcUbqAQxxgD4b3iA6BLbF0YKGofnWrMtXBBWI8X0jekxncu7sWdBuieyhg33fik=
+  on:
+    tags: true
+    repo: chaijs/chai

CONTRIBUTING.md

@@ -11,6 +11,7 @@ Following these guidelines helps to communicate that you respect the time of the
   - [Bug Reports](#bugs)
   - [Feature Requests](#features)
   - [Pull Requests](#pull-requests)
+- [Releasing](#releasing)
 - [Support](#support)
   - [Resources](#resources)
   - [Core Contributors](#contributors)
@@ -136,6 +137,30 @@ git push origin <topic-branch-name>
 
 **IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.
 
+<a name="releasing"></a>
+## Releasing
+
+Releases can be prepared by any core-contributor or user whom has push access to
+the `chaijs/chai` repository.
+
+This process requires [git-extras](https://github.com/tj/git-extras) for some steps.
+
+1. Ensure all tests pass.
+2. Bump the version tag in-code and for all package managers.
+  - `lib/chai.js`
+  - `package.json`
+  - `component.json`
+  - `bower.json`
+3. Build the browser version with `make`.
+4. Append commit log to `HISTORY.md` using `git changelog` command.
+5. Write human-friendly `ReleaseNotes.md` based on changelog.
+  - If breaking changes, write migration tutorial(s) and reasoning.
+  - Callouts for community contributions (PRs) with links to PR and contributing user.
+  - Callouts for other fixes made by core contributors with links to issue.
+6. Update `README.md` with an updated contributors list using `git summary` command.
+7. Push a tagged release using `git release x.x.x`.
+  - All tagged releases are published to NPM.
+
 <a name="support"></a>
 ## Support