doc: update for v1.0.0-rc.2 (#115)

Signed-off-by: Junjie Gao <junjiegao@microsoft.com>

README.md

@@ -16,7 +16,7 @@ Before you begin, make sure the latest version of the [Notation CLI has been ins
 
    For Linux Bash:
    ```bash
-   version=1.0.0-rc.1
+   version=1.0.0-rc.2
    arch=amd64
    install_path="${HOME}/.config/notation/plugins/azure-kv"
 
@@ -36,7 +36,7 @@ Before you begin, make sure the latest version of the [Notation CLI has been ins
 
    For macOS Zsh:
    ```zsh
-   version=1.0.0-rc.1
+   version=1.0.0-rc.2
    arch=arm64
    install_path="${HOME}/Library/Application Support/notation/plugins/azure-kv"
 
@@ -52,14 +52,11 @@ Before you begin, make sure the latest version of the [Notation CLI has been ins
    # install the plugin
    mkdir -p ${install_path}
    tar xvzf ${tar_file} -C ${install_path} notation-azure-kv
-
-   # ad-hoc sign the binary
-   codesign -s - ${install_path}/notation-azure-kv
    ```
 
    For Windows Powershell:
    ```powershell
-   $version = "1.0.0-rc.1"
+   $version = "1.0.0-rc.2"
    $arch = "amd64"
    $install_path = "${env:AppData}\notation\plugins\azure-kv"
 

RELEASE_CHECKLIST.md

@@ -6,9 +6,10 @@ This document describes the checklist to publish a release via GitHub workflow.
 
 ## Release Process
 1. Determine a [SemVer2](https://semver.org/)-valid version prefixed with the letter `v` for release. For example, `version="v1.0.0-rc.1"`.
-2. Be on the main branch connected to the actual repository (not a fork) and `git pull`.  Ensure `git log -1` shows the latest commit on the main branch.
-3. Create a tag `git tag -am $version $version`
-4. `git tag` and ensure the name in the list added looks correct, then push the tag directly to the repository by `git push --follow-tags`.
-5. Wait for the completion of the GitHub action [release-github](https://github.com/Azure/notation-azure-kv/actions/workflows/release.yml).
-6. Check the new draft release, revise the release description, and publish the release.
-7. Announce the release in the community.
+2. Submit a PR to update the `version` in `README.md` and wait approval for merging.
+3. Be on the main branch connected to the actual repository (not a fork) and `git pull`.  Ensure `git log -1` shows the latest commit on the main branch.
+4. Create a tag `git tag -am $version $version`
+5. `git tag` and ensure the name in the list added looks correct, then push the tag directly to the repository by `git push --follow-tags`.
+6. Wait for the completion of the GitHub action [release-github](https://github.com/Azure/notation-azure-kv/actions/workflows/release.yml).
+7. Check the new draft release, revise the release description, and publish the release.
+8. Announce the release in the community.