docs: Update docs instructions [ci skip]
Triager Bot takes care of making pull requests to get the docs from `appium/appium` into `appium/appium.io` for us.
Updating the release instructions to get rid of the updating site docs documentation and updating the release instructions to instruct to just merge in the latest.
MODIFY
docs/en/contributing-to-appium/developers-overview.md
docs/en/contributing-to-appium/developers-overview.md
@@ -139,21 +139,6 @@ _FORCE_LOGS=1 <command> # show module log output during test run
Note that we have a convention for unit test files to end in `-specs.js` and
for e2e test files to end in `-e2e-specs.js`.
-### Updating Appium site docs
-
-The [Appium site](https://appium.io) is built using a site generator that translates the markdown in https://github.com/appium/appium to static HTML
-
-To update the site docs, follow these steps:
-
-1. From Appium repo, run `npm run generate-docs` and make a pull request if there are any newly generated docs.
-1. When the above PR is merged, clone the [appium.io](https://github.com/appium/appium.io) repo (if you haven't done so already)
-1. Check out and pull the latest `gh-pages` branch
-1. Follow the setup guide in the README.md
-1. Generate the docs by running `npm run build:docs`
-1. Make a new branch
-1. Commit and push changes and make a pull request to have changes merged into `gh-pages`
-
-
### Releasing
The release process for any Appium module other than the main Appium package is
@@ -198,9 +183,9 @@ converted into the `npm-shrinkwrap.json` file.
1. Run `npm shrinkwrap` to generate the `npm-shrinkwrap.json`
1. Create a tag of the form `v<version>` on the release branch (usually a minor branch like `1.5` or `1.4`), with: `git tag -a v<version>`, e.g., `git tag -a v1.5.0`. This is not necessary for beta versions.
1. Push the tag to upstream: `git push --tags <remote> <branch>`
-1. Run `npm publish` (with `--tag beta` if this isn't an official release).
+1. Run `npm publish` (with `--tag rc` if this isn't an official release).
1. Remove the NPM shrinkwrap JSON file from Git and push the changes
-1. Update the site docs (see "Updating Appium site docs" above) or put in an [issue](https://github.com/appium/appium/issues) to have the site docs updated
+1. Update the site docs by going to https://github.com/appium/appium.io/pulls and merging the latest pull request that was opened by the Triager bot. Close any other pull requests opened by Triager bot.
1. Create a new release on GitHub: go to `https://github.com/appium/appium/releases/tag/v<VERSION>` and hit "Edit Tag". Make the release name `<VERSION>` (e.g., `2.0.5`), then paste in the changelog (but not the changelog header for this version). If it's a beta release, mark as pre-release.
1. Create a new post on discuss.appium.io announcing the release. Post it in the "News" category. Paste in the changelog and any choice comments. Pin it and unpin the previous release post.
1. Begin process of releasing `appium-desktop`.

docs: Update docs instructions [ci skip] (#12351)

Triager Bot takes care of making pull requests to get the docs from `appium/appium` into `appium/appium.io` for us.

Updating the release instructions to get rid of the updating site docs documentation and updating the release instructions to instruct to just merge in the latest.