From 926e96aca4aa4bce32e9ff0df679c9755aabd23a Mon Sep 17 00:00:00 2001
From: salonichf5 <146118978+salonichf5@users.noreply.github.com>
Date: Thu, 12 Jun 2025 15:07:25 -0600
Subject: [PATCH] update release doc with more info

---
 docs/developer/release-process.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/developer/release-process.md b/docs/developer/release-process.md
index 3c02054674..1297d0b83b 100644
--- a/docs/developer/release-process.md
+++ b/docs/developer/release-process.md
@@ -54,7 +54,15 @@ To create a new release, follow these steps:
       the [GitHub releases](https://github.com/nginx/nginx-gateway-fabric/releases) after the release branch is
       created. If included, use the Release Notes specified in a PR.
       - If the supported Gateway API minor version has changed since the last release, add a note to the release notes explaining if the previous version is no longer supported.
-6. Ensure you are on the latest version of the release branch and are up-to-date on all commits, then create and push the release tag in the format `vX.Y.Z`. As a result, the CI/CD pipeline will:
+      - Merge the release PR once it has received all necessary approvals.
+6. Ensure you are on the latest version of the release branch and are up-to-date on all commits, then create and push the release tag in the format `vX.Y.Z`.
+
+   ```shell
+   git tag vX.Y.Z
+   git push upstream vX.Y.Z
+   ```
+
+   As a result, the CI/CD pipeline will:
    - Build NGF, NGINX and NGINX Plus container images with the release tag `X.Y.Z` and push them to the registries.
    - Package and publish the Helm chart to the registry.
    - Create a GitHub release with an autogenerated changelog and attached release artifacts.