From b5332ac32f7ef164ebbfb21a9194348e0e108129 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Irene=20Rodr=C3=ADguez?= Date: Tue, 10 Dec 2024 11:07:46 +0100 Subject: [PATCH] Fix broken link (#919) The previous link pointed to the old wiki. --- docs/sources/contribute/release-notes/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/contribute/release-notes/index.md b/docs/sources/contribute/release-notes/index.md index 0ba1cd887..085ac0ab2 100644 --- a/docs/sources/contribute/release-notes/index.md +++ b/docs/sources/contribute/release-notes/index.md @@ -43,7 +43,7 @@ _Quality assurance is a conversation within and between contributing teams and i Enter release notes into the CMS two to four weeks before the feature is available, depending on the size of the product or feature. This gives the Go To Market (GTM) team time for promotion and enablement. For Grafana versioned releases, have your content entered in the CMS by the cut-off date communicated by the delivery team. -For more information, refer to the [Record Announce Document Ship (RADS) guidelines](https://grafana-intranet--simpplr.vf.force.com/apex/simpplr__app?u=/site/a145f000001dCXBAA2/page/a125f000004oOF7AAM). +For more information, refer to the [Record Announce Document Ship (RADS) guidelines](https://wiki.grafana-ops.net/w/index.php/Engineering/RADS). It's important to understand that, in the context of the CMS, the word "published" has a slightly different meaning than in general use: