Release v4.18

We are working on the next v4.18 release.

• Checkout if we have major or minor changes.
• Who should make the release?
• Set timeframe for the new release.
• Identify major bugs and add them to the 4.18 milestone.
• Fix major bugs and complete milestone v4.18.

Official Release Checklist

Build

• Change the version number of the library in package.json.
• Open HISTORY.md, write down the changes, version number, and release date.
• Build the library by running: npm prune, npm update and npm run build

Test

• Test the library: npm test
• Open some of the examples in your browser and visually check if it works as expected.

Commit

• Commit the changes to the develop branch.
• Rebase the master branch on the develop branch.
• Create a version tag (with the new version number): git tag v4.18.0
• Push the branches to github
• Push it to github: git push --tags

Publish

• Publish at npm: npm publish
• Test the published library:
  • Go to a temp directory
  • Install the library from npm: npm install vis

Verify if it installs the just released version, and verify if it works.

• Install the library via bower: bower install vis
• Verify if it installs the just released version, and verify if it works.
• Verify within a day or so whether vis.js is updated on http://cdnjs.com/

Update website

• Copy the dist folder from the master branch to the github-pages branch.
• Copy the docs folder from the master branch to the github-pages branch.
• Copy the examples folder from the master branch to the github-pages branch.
• Check if there are new or updated examples, and update the gallery screenshots accordingly.
• Update the library version number in the index.html page.
• Update the CDN links at the download section of index.html AND the CDN link at the top. (replace all)
• Commit the changes in the gh-pages branch.

Prepare next version

• Switch to the develop branch.
• Change version numbers in package.json to a snapshot version like 4.18.0-SNAPSHOT.