Release Guide - vistone/cesium_Language_cn GitHub Wiki

We release Cesium on the first work day of every month. Releases are available on the downloads page.

There is no release manager; instead, our community shares the responsibility. Any committer can create the release for a given month, and at any point, they can pass the responsibility to someone else, or someone else can ask for it. This spreads knowledge, avoids stratification, avoids a single point of failure, and is beautifully unstructured.

Release testing and packaging

  1. Verify there are no show stopper issues.
  2. Send a courtesy message to the forum to let people know you're about to start the release process.
  3. Make sure you are using the latest drivers for your video card.
  4. Pull down the latest master branch.
  5. Update CHANGES.md with the date of the release. Also give it a final proof read and tweaking. Adjust the order of changes so that prominent/popular changes come first.
  6. Update build.xml with the version being released, e.g., <property name="version" value="b7" />
  7. Commit these changes.
  8. Make sure the repository is clean git clean -d -x -f. This will delete all files not already in the repository.
  9. Create the release zips and start the server for testing ./Tools/apache-ant-1.8.2/bin/ant makeZipFile runServer
  10. Verify that the Documentation built correctly
  11. If running on Windows, each browser should be tested with ANGLE enabled. The state of ANGLE can be verified using WebGL Report.
  12. Run unit tests in Chrome stable.
  13. Run unit tests in Firefox stable.
  14. Make sure Hello World loads.
  15. Make sure Cesium Viewer loads.
  16. Run Sandcastle on the browser of your choice (or multiple browsers if you are up for it) and run through each demo to make sure they all work. Actually play with each of the buttons and sliders on each demo to ensure everything works as expected.
  17. If any of the above steps fail, contact the forum to figure out what needs to be fixed before we can release. Do NOT proceed to the next step until issues are resolved.
  18. Create and push a tag, e.g.,
    • git tag -a b7 -m 'b7 release'
    • git push --tags
  19. Branch the website and open a pull request for release with post and release zips. See the Adding a New Cesium Release section of the website wiki.
  20. Reply to your courtesy message on the forum to let everyone know the release is ready.

Also, see our release discussion on the forum.