Checklist Release

1. Set correct version in Version.js and commit
2. Create a tag

• Via github interface or
• via git commandline commands
• Naming convention for the release tags is vmajor.minor.patch.label (e. g. v2.0.1.beta3)

3. The description of the tag can be generated e.g. with https://www.npmjs.org/package/github-changelog
4. Update API-docs on github.io

• Edit jsduck.json --> the version in the title should be updated
• For the API-docs with ExtJS classes make sure you have a local copy of ExtJS
• Build both (with and without ExtJS) docs with jsduck: Comment and uncomment the relevant parts in the jsduck.json
• The content generated in the doc folders (docs and docs-w-ext) replaces the content of the respective folders in the gh-pages branch

4. Edit index.html of gh-pages branch to reference the new version
5. Update the src/ folder of the gh-pages-branch with the current src/ of the master branch (So that the examples will report the correct version in GeoExt.version)
6. Write a blog post
7. Email the dev and users lists and announce the release containing:
   • A link to the tag on github
   • A summary of the major features and bug fixes for the release
8. Write a 50 word summary of the release and send to news_item at osgeo dot org (see http://www.osgeo.org/content/news/submit_news.html)