update docs

Author: clarasb

chartlets.js/package-lock.json

@@ -81,6 +81,30 @@ mkdocs build
 mkdocs gh-deploy
 ```
 
+## Release on GitHub
+
+This describes the release process for chartlets.
+
+- Check issues in progress, close any open issues that have been fixed.
+- Make sure that all unit tests pass and that test coverage is 100% (or as near to 100% as practicable).
+- In `chartlets.py/chartlets/version.py`, `chartlets.js/packages/lib/package.json` and `chartlets.js/packages/demo/package.json` remove the .dev suffix from version name.
+- Make sure `CHANGES.md` is complete in both `chartlets.js` and `chartlets.py`. Remove the suffix (in development) from the last version headline.
+- Push changes to either main or a new maintenance branch and merge (see above).
+- Await results from Github Action workflow.
+- Go to `chartlets/releases` and press button `“Draft a new Release”`.
+    - Tag version is: `v${version}` (with a “v” prefix)
+    - Release title is: `${version}` (without a “v” prefix)
+    - Paste latest changes from `CHANGES.md` into field `“Describe this release”`
+    - Press `“Publish release”` button
+- After the release on GitHub, the Github Actions CI would run to publish both
+  `chartlets.py` to `PyPi` and `chartlets.js` to `npm`.
+- Create a new maintenance branch (see above)
+- In `chartlets.py/chartlets/version.py`, `chartlets.js/packages/lib/package.json` and `chartlets.js/packages/demo/package.json` increase version number and append a .dev0 suffix to the version name so that it is still PEP-440 compatible.
+- In `CHANGES.md` add a new version headline and attach (in development) to it.
+- Push changes to either main or a new maintenance branch (see above).
+- Activate new doc version on mkdocs
+
+
 ## License
 
 Chartlets is open source made available under the terms and conditions of the