updating release issue-template (#361)

Signed-off-by: Kellen Swain <kfswain@google.com>

Author: kfswain

.github/ISSUE_TEMPLATE/new-release.md

@@ -21,7 +21,7 @@ This document defines the process for releasing llm-d-inference-scheduler.
 
 1. Permissions to push to the llm-d-inference-scheduler repository.
 
-2. Set the required environment variables based on the expected release number:
+1. Set the required environment variables based on the expected release number:
 
    ```shell
    export MAJOR=0
@@ -30,23 +30,24 @@ This document defines the process for releasing llm-d-inference-scheduler.
    export REMOTE=origin
    ```
 
-3. If creating a release candidate, set the release candidate number.
+1. If creating a release candidate, set the release candidate number.
 
    ```shell
    export RC=1
    ```
-
-## Release Process
-
 1. If needed, clone the llm-d-inference-scheduler [repo].
 
    ```shell
    git clone -o ${REMOTE} git@github.com:llm-d/llm-d-inference-scheduler.git
    ```
 
-2. If you already have the repo cloned, ensure it’s up-to-date and your local branch is clean.
+## Release Process
+
+### Create or Checkout branch 
+
+1. If you already have the repo cloned, ensure it’s up-to-date and your local branch is clean.
 
-3. Release Branch Handling:
+1. Release Branch Handling:
    - For a Release Candidate:
      Create a new release branch from the `main` branch. The branch should be named `release-${MAJOR}.${MINOR}`, for example, `release-0.1`:
 
@@ -61,29 +62,15 @@ This document defines the process for releasing llm-d-inference-scheduler.
      git checkout -b release-${MAJOR}.${MINOR} ${REMOTE}/release-${MAJOR}.${MINOR}
      ```
 
-4. Update release-specific content, generate release artifacts, and stage the changes.
-
-5. Sign, commit, and push the changes to the `llm-d-inference-scheduler` repo.
-
-   For a release candidate:
-
-    ```shell
-    git commit -s -m "Updates artifacts for v${MAJOR}.${MINOR}.${PATCH}-rc.${RC} release"
-    ```
-
-   For a major, minor or patch release:
-
-    ```shell
-    git commit -s -m "Updates artifacts for v${MAJOR}.${MINOR}.${PATCH} release"
-    ```
-
-6. Push your release branch to the llm-d-inference-scheduler remote.
+1. Push your release branch to the llm-d-inference-scheduler remote.
 
     ```shell
     git push ${REMOTE} release-${MAJOR}.${MINOR}
     ```
 
-7. Tag the head of your release branch with the number.
+### Tag commit and trigger image build
+
+1. Tag the head of your release branch with the sem-ver release version.
 
    For a release candidate:
 
@@ -97,7 +84,7 @@ This document defines the process for releasing llm-d-inference-scheduler.
     git tag -s -a v${MAJOR}.${MINOR}.${PATCH} -m 'llm-d-inference-scheduler v${MAJOR}.${MINOR}.${PATCH} Release'
     ```
 
-8. Push the tag to the llm-d-inference-scheduler repo.
+1. Push the tag to the llm-d-inference-scheduler repo.
 
    For a release candidate:
 
@@ -111,15 +98,18 @@ This document defines the process for releasing llm-d-inference-scheduler.
     git push ${REMOTE} v${MAJOR}.${MINOR}.${PATCH}
     ```
 
-9. Pushing the tag triggers CI action to build and publish the container image to the [ghcr registry].
-10. Test the steps in the tagged quickstart guide after the PR merges. TODO add e2e tests! <!-- link to an e2e tests once we have such one -->
-11. Create a [new release]:
+1. Pushing the tag triggers CI action to build and publish the container image to the [ghcr registry].
+1. Test the steps in the tagged quickstart guide after the PR merges. TODO add e2e tests! <!-- link to an e2e tests once we have such one -->
+
+### Create the release!
+
+1. Create a [new release]:
     1. Choose the tag that you created for the release.
-    2. Use the tag as the release title, i.e. `v0.1.0` refer to previous release for the content of the release body.
-    3. Click "Generate release notes" and preview the release body.
-    4. Go to Gateway Inference Extension latest release and make sure to include the highlights in llm-d-inference-scheduler as well.
-    5. If this is a release candidate, select the "This is a pre-release" checkbox.
-12. If you find any bugs in this process, create an [issue].
+    1. Use the tag as the release title, i.e. `v0.1.0` refer to previous release for the content of the release body.
+    1. Click "Generate release notes" and preview the release body.
+    1. Go to Gateway Inference Extension latest release and make sure to include the highlights in llm-d-inference-scheduler as well.
+    1. If this is a release candidate, select the "This is a pre-release" checkbox.
+1. If you find any bugs in this process, create an [issue].
 
 ## Announce the Release
 
@@ -131,9 +121,9 @@ Use the following steps to announce the release.
    [ANNOUNCE] llm-d-inference-scheduler v${MAJOR}.${MINOR}.${PATCH} is released
    ```
 
-2. Add a link to the final release in this issue.
+1. Add a link to the final release in this issue.
 
-3. Close this issue.
+1. Close this issue.
 
 [repo]: https://github.com/llm-d/llm-d-inference-scheduler
 [ghcr registry]: https://github.com/llm-d/llm-d-inference-scheduler/pkgs/container/llm-d-inference-scheduler