shanpin/chat-server: 语音房 @ bf846a7082d087a8d8f824df1a91d1a36870a7fa

mongoose release procedure

tests must pass
update package.json version
update History.md using git changelog or similar. list the related ticket(s) # as well as a link to the github user who fixed it if applicable.
git commit -m 'release x.x.x'
git tag x.x.x
git push origin BRANCH --tags && npm publish
update mongoosejs.com (see "updating the website" below)
announce to google groups - include the relevant change log and links to issues
tweet google group announcement from @mongoosejs
change package.json version to next patch version suffixed with '-pre' and commit "now working on x.x.x"
if this is a stable release, update the unstable History.md with the changelog

For 4.x

Change to the master branch
execute make docs (when this process completes you'll be on the gh-pages branch)
`git commit -a -m 'website; regen <4.x.x>'
git push origin gh-pages

For 3.8.x:

Change to the 3.8.x branch
execute make docs_legacy (when this process completes you'll be on the gh-pages branch)
git commit -a -m 'website; regen <x.x.x>'
git push origin gh-pages