Update RELEASE doc

Author: EzraBrooks

RELEASE.md

@@ -1,7 +1,4 @@
-# Robot Web Tools Module Release TODOs
-
-This document describes TODOs and checklists in order to release
-Robot Web Tool javascript modules([roslibjs](https://github.com/RobotWebTools/roslibjs), [ros2djs](https://github.com/RobotWebTools/ros2djs), [ros3djs](https://github.com/RobotWebTools/ros3djs)).
+# How to release roslibjs
 
 ## 0. Make sure that the releasing module is compatible with other RWT modules
 
@@ -13,36 +10,14 @@ docker run -it --rm -v "$(pwd)":/usr/local/src/your-app githubchangeloggenerator
 
 ## 2. Bump a new version
 
-* Version bump in package.json, bower.json, and in the main file. e.g) [RosLib.js](src/RosLib.js)
+* Version bump in [package.json](./package.json)
 * Tag the version
 
-## 3. Release modules
-
-### NPM
-
-Publish the module. We publish in the global scope.
-
-* `npm publish`
-
-### CDN
-
-Hosted via the [JsDelivr](https://www.jsdelivr.com/) CDN, which takes it directly from the repo.
-
-## 4. Create GitHub Release
+## 3. Create GitHub Release
 
 * Create a new GitHub release based on the new git tag.
 * Add the version number as release title (Without leading `v`).
 * Let GitHub auto-generate the Changelog
 * Mark `Set as latest release`
 * Publish release
-
-## 5. Update JSdocs in Robot Web Tools website
-
-The JSdocs are update automatically by GitHub Actions [config](.github/workflows/docs.yml). The GitHub release created above, will trigger this run. The docs are hosted in their own repository at the `gh-pages` branch.
-
-## 6. Sync `develop` branch with `master`
-
-`Master` branch should represent the latest release.
-
-* Create a PR against `master` from `develop`
-* Do *Rebase and merge* to have the same history as `develop` branch
+* [The CD action](.github/workflows/cd.yml) will automatically publish the docs to the website and publish the package to npm.