From de0e6d925df5da65906c008cd8ce483986635c73 Mon Sep 17 00:00:00 2001 From: Saylor Berman Date: Tue, 11 Jun 2024 09:12:58 -0600 Subject: [PATCH] Update release doc for conformance --- docs/developer/release-process.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/developer/release-process.md b/docs/developer/release-process.md index c1ad4503d9..36ae6e099c 100644 --- a/docs/developer/release-process.md +++ b/docs/developer/release-process.md @@ -63,8 +63,7 @@ To create a new release, follow these steps: 14. Verify that published artifacts in the release can be installed properly. 15. Submit the `conformance-profile.yaml` artifact from the release to the [Gateway API repo](https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports). - Create a fork of the repository - - Name the file `-report.yaml` and set `gatewayAPIVersion` in the file to the - supported version by NGF. Update the README in the ngf directory and update the site source if necessary (see following example). + - Name the file based on the requirements of the [README](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/README.md). Update the README in the ngf directory and update the site source if necessary (see following example). - Open a PR. [Example](https://github.com/kubernetes-sigs/gateway-api/pull/2514) If it's your first time submitting a PR, you will need to sign a CLA using F5, Inc. as the organization.