Revert "docs: remove step to create discussion page" (#42)

* Revert "docs: remove step to create discussion page (#41)"

This reverts commit 415e658.

* add discussions link to README.md

README.md

@@ -123,13 +123,13 @@ To engage with the Alloy community:
   Grafana Slack, visit <https://slack.grafana.com/> and join the `#alloy`
   channel.
 
-* Ask questions on the [Grafana community website][community].
+* Ask questions on the [Discussions page][discussions].
 
 * [File an issue][issue] for bugs, issues, and feature suggestions.
 
 * Attend the monthly [community call][community-call].
 
-[community]: https://community.grafana.com
+[discussions]: https://github.com/grafana/agent/discussions
 [issue]: https://github.com/grafana/alloy/issues/new
 [community-call]: https://docs.google.com/document/d/1TqaZD1JPfNadZ4V81OCBPCG_TksDYGlNlGdMnTWUSpo
 

docs/developer/release/6-publish-release.md

@@ -15,14 +15,15 @@ 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!
+6. Publish the release!