From 0db36f6f52f9af70edc991415dc77c7581c161b7 Mon Sep 17 00:00:00 2001 From: Robert Fratto Date: Tue, 19 Mar 2024 11:34:33 -0400 Subject: [PATCH] docs: remove step to create discussion page At least for now, the idea is to focus discussion towards , so discussions have been disabled in the Alloy repo. --- docs/developer/release/6-publish-release.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/developer/release/6-publish-release.md b/docs/developer/release/6-publish-release.md index 48a492aeb4..d36b828d8c 100644 --- a/docs/developer/release/6-publish-release.md +++ b/docs/developer/release/6-publish-release.md @@ -15,15 +15,14 @@ This is how to publish the release in GitHub. 3. Add a footer to the `Notable Changes` section: `For a full list of changes, please refer to the [CHANGELOG](https://github.com/grafana/agent/blob/RELEASE_VERSION/CHANGELOG.md)!` - - Do not substitute the value for `CHANGELOG`. + + Do not substitute the value for `CHANGELOG`. 4. At the bottom of the release page, perform the following: - - Tick the check box to "add a discussion" under the category for "announcements". - For a Release Candidate, tick the checkbox to "pre-release". - For a Stable Release or Patch Release, tick the checkbox to "set as the latest release". 5. Optionally, have other team members review the release draft if you wish to feel more comfortable with it. -6. Publish the release! \ No newline at end of file +6. Publish the release!