vis.js is a dynamic, browser-based visualization library
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

80 lines
1.9 KiB

10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
  1. # How to publish vis.js
  2. This document describes how to publish vis.js.
  3. ## Build
  4. - Change the version number of the library in both `package.json` and `bower.json`.
  5. - Open `HISTORY.md`, write down the changes, version number, and release date.
  6. - Build the library by running:
  7. npm update
  8. npm run build
  9. This generates the vis.js library in the folder `./dist`.
  10. ## Test
  11. - Test the library:
  12. npm test
  13. - Open some of the example in your browser and visually check if it works as expected.
  14. ## Commit
  15. - Commit the changes to the `develop` branch.
  16. - Merge the `develop` branch into the `master` branch.
  17. - Push the brances to github
  18. - Create a version tag (with the new version number) and push it to github:
  19. git tag v0.3.0
  20. git push --tags
  21. ## Publish
  22. - Publish at npm:
  23. npm publish
  24. - Test the published library:
  25. - Go to a temp directory
  26. - Install the library from npm:
  27. npm install vis
  28. Verify if it installs the just released version, and verify if it works.
  29. - Install the libarry via bower:
  30. bower install vis
  31. Verify if it installs the just released version, and verify if it works.
  32. ## Update website
  33. - Copy the `dist` folder from the `master` branch to the `github-pages` branch.
  34. - Copy the `examples` folder from the `master` branch to the `github-pages` branch.
  35. - Copy the `docs` folder from the `master` branch to the `github-pages` branch.
  36. - Create a packaged version of vis.js. Go to the `master` branch and run:
  37. zip vis.zip dist docs examples README.md HISTORY.md LICENSE NOTICE -r
  38. - Move the created zip file `vis.zip` to the `download` folder in the
  39. `github-pages` branch. TODO: this should be automated.
  40. - Go to the `github-pages` branch and run the following script:
  41. node updateversion.js
  42. ## Prepare next version
  43. - Switch to the `develop` branch.
  44. - Change version numbers in `package.json` and `bower.json` to a snapshot
  45. version like `0.4.0-SNAPSHOT`.