From c918b754a59a7b781dc52865055de9be63e29300 Mon Sep 17 00:00:00 2001 From: Kemal Akkoyun Date: Thu, 23 Jan 2025 16:37:46 +0100 Subject: [PATCH] chore(docs): Add links for the upstream PRs Add example PR links to RELEASE.md Signed-off-by: Kemal Akkoyun --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 1afb6246d..d6d3b9569 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -59,8 +59,8 @@ We use [Semantic Versioning](https://semver.org/). 7a. For Release Candidates: - Release RC GitHub release with "pre-release" box checked - Click "Publish release"! - - Create PR against [prometheus/prometheus](https://github.com/prometheus/prometheus) using RC version - - Create PR against [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) using RC version + - Create PR against [prometheus/prometheus](https://github.com/prometheus/prometheus) using RC version (e.g. https://github.com/prometheus/prometheus/pull/15851) + - Create PR against [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) using RC version (e.g. https://github.com/kubernetes/kubernetes/pull/129752) - Make sure the CI is green for the PRs - Allow 1-2 days for downstream testing - Fix any issues found before final release