Restore RELEASE_PROCESS.md

Will update it in main after this release is done

Signed-off-by: Christian Kadner <ckadner@us.ibm.com>

release/RELEASE_PROCESS.md

@@ -17,46 +17,33 @@ In general, unless you're committing code that only applies to the release strea
 If you aren't already working on a release branch (of the form `release-${MAJOR}`, where `release-${MAJOR}` is a major-minor version number), then create one.
 Release branches serve several purposes:
 
-1. They allow a release wrangler or other developers to focus on a release without interrupting development on `main`,
-2. They allow developers to track the development of a release before a release candidate is declared,
-3. They simplify back porting critical bug fixes to a patch level release for a particular release stream (e.g., producing a `v0.6.1` from `release-0.6`), when appropriate.
-
-These 3 repositories need a release branch:
-- [`modelmesh-serving`](https://github.com/kserve/modelmesh-serving/branches)
-- [`modelmesh`](https://github.com/kserve/modelmesh/branches)
-- [`modelmesh-runtime-adapter`](https://github.com/kserve/modelmesh-runtime-adapter/branches)
+1.  They allow a release wrangler or other developers to focus on a release without interrupting development on `main`,
+1.  They allow developers to track the development of a release before a release candidate is declared,
+1.  They simplify back porting critical bug fixes to a patch level release for a particular release stream (e.g., producing a `v0.6.1` from `release-0.6`), when appropriate.
 
 ## Publish the release
 
-It's generally a good idea to search the repo or `control`-`shift`-`f` for strings of the old version number and replace them with the new, keeping in mind conflicts with other library version numbers.
-
-The steps below should be performed at least twice -- once for the release candidate(s) (`v0.10.0-rc0`,
-`v0.10.0-rc1`, ...) and once more for the actual release (`v0.10.0`).
+It's generally a good idea to search the repo or control-f for strings of the old version number and replace them with the new, keeping in mind conflicts with other library version numbers.
 
-1. Create new (pre-)release tags (v...`-rc0`) in the [`modelmesh`](https://github.com/kserve/modelmesh/releases) and [`modelmesh-runtime-adapter`](https://github.com/kserve/modelmesh-runtime-adapter/releases) repositories on the newly created release branches. This can be done by creating a draft release using the GitHub web interface and checking the "Set as a pre-release" option. The newly created tag should trigger the GitHub action to push the respective (pre-)release container images to DockerHub which are needed in the next step.
-2. In this `modelmesh-serving` repository, update the container image tags for `modelmesh`, `modelmesh-runtime-adapter`, `modelmesh-controller`, and `rest-proxy` to the corresponding release version numbers:
+1. Update `modelmesh`, `modelmesh-runtime-adapter`, `modelmesh-controller`, and `rest-proxy` image tags to the corresponding release version numbers.
    - Edit `newTag` in `config/manager/kustomization.yaml`.
    - Edit the `modelmesh`, `modelmesh-runtime-adapter`, and `rest-proxy` image tags in `config/default/config-defaults.yaml`.
    - Edit the `config/dependencies/quickstart.yaml` file, changing the `kserve/modelmesh-minio-examples` image tag to use the pinned version.
    - Edit the `docs/component-versions.md` file with the version and component versions.
    - Edit the `docs/install/install-script.md` file, updating the `RELEASE` variable in the `Installation` section to the new release branch name.
    - Edit the `docs/quickstart.md` file, updating the `RELEASE` variable in the `Get the latest release` section to the new release branch name.
    - Edit the `scripts/setup_user_namespaces.sh` file, changing the `modelmesh_release` version.
-3. Submit your PR to the `release-*` branch that was created earlier and wait for it to merge.
-4. Update `docs/component-versions.md`, `docs/quickstart.md`, `docs/install/install-script.md`, and `scripts/setup_user_namespaces.sh` files in the main branch with the same versions as above, then submit this as a PR to `main`. Wait for this to merge.
-5. Generate release manifests:
+1. Submit your PR to the release branch and wait for it to merge.
+1. Update `docs/component-versions.md`, `docs/quickstart.md`, `docs/install/install-script.md`, and `scripts/setup_user_namespaces.sh` files in the main branch with the same versions as above, then submit this as a PR to `main`. Wait for this to merge.
+1. Generate release manifests:
    - `kustomize build config/default > modelmesh.yaml`
    - `kustomize build config/runtimes --load-restrictor LoadRestrictionsNone > modelmesh-runtimes.yaml`
    - `cp config/dependencies/quickstart.yaml modelmesh-quickstart-dependencies.yaml`
-6. Generate config archive:
+1. Generate config archive:
    - Run one of the following depending on what version of `tar` you have. Be sure to replace the `update-me` below with the correct version:
-     - GNU tar: `RELEASE=update-me;tar -zcvf config-${RELEASE}.tar.gz config/ --transform s/config/config-${RELEASE}/`
-     - BSD tar: `RELEASE=update-me;tar -zcvf ${RELEASE}.tar.gz -s /config/${RELEASE}/ config/`
-7. Once everything has settled, tag and push the release with `git tag $VERSION` and `git push upstream $VERSION`. You can also tag the release in the GitHub UI.
+      - GNU tar: `RELEASE=update-me;tar -zcvf config-${RELEASE}.tar.gz config/ --transform s/config/config-${RELEASE}/`
+      - BSD tar: `RELEASE=update-me;tar -zcvf ${RELEASE}.tar.gz -s /config/${RELEASE}/ config/`
+1. Once everything has settled, tag and push the release with `git tag $VERSION` and `git push upstream $VERSION`. You can also tag the release in the GitHub UI.
    - The `modelmesh-controller` image will be published via GitHub Actions.
-8. Upload generated install manifests to GitHub release assets.
-9. Be sure to create and push a new tag for the `kserve/modelmesh-minio-examples` image.
-
-
-## TODOs
-- [ ] build and push `kserve/modelmesh-minio-examples:v0.10.0`
+1. Upload generated install manifests to GitHub release assets.
+1. Be sure to create and push a new tag for the `kserve/modelmesh-minio-examples` image.