Release process

In theory the release.sh script is supposed to do everything. In practice there are a few things you need to do manually.

Here's the procedure that @danvk used for the 1.1.0 update:

git checkout -b release-1.1.0  # create release branch
# update releases.json
# update package.json
# update bower.json
# update README version
# update dygraph.js version
# update docs/versions.html
git commit -a -m 'Bump versions and add release notes'
git checkout master
git merge release-1.1.0  # merge release notes back onto master

# Now create distribution files on release branch; these don't go back into master.
git checkout release-1.1.0
./generate-combined.sh cat-dev > dygraph-combined-dev.js
./generate-combined.sh
git add .
git commit -a -m 'Generate combined files for distribution'

# Do the release. This will update dygraphs.com and push the release tag to GitHub.
./release.sh 1.1.0

# Merge the new release onto the releases branch and update NPM.
# bower updates automatically using the github tag.
git checkout releases
git merge release-1.1.0
npm publish

At the end of the process, verify that:

• dygraphs.com has the newest release on the download page.
• The NPM listing has the newest release.
  Running npm install should put dygraph-combined.js in node_modules/dygraphs/dygraph-combined.js.
• Bower has picked up the new release (look at "Last updated" on this page).
  Running bower install dygraphs should put dygraph-combined.js in bower_components/dygraphs/dygraph-combined.js.
• cdnjs has picked up the change. It should check for new github tags every ~15 minutes.