diff --git a/Release-Guidelines.md b/Release-Guidelines.md index 06a548f..14a9790 100644 --- a/Release-Guidelines.md +++ b/Release-Guidelines.md @@ -57,7 +57,9 @@ After any release is published, the following things should be done: * Make sure all the new functionality is documented on the wiki * Mark deprecated features appropriately * Remove all `unreleased` notes from the wiki -* Inform packagers of new release, specifically mention dependency changes. Look through the `Packaging` issue tag for packagers [here](https://github.com/polybar/polybar/issues?q=is%3Aissue+label%3APackaging+is%3Aopen). +* Inform packagers of new release in + [`#1971`](https://github.com/polybar/polybar/issues/1971). Mention any + dependency changes and any changes to the build workflow. * Create a source archive named `polybar-@POLYBAR_VERSION@.tar` that includes the submodule source code with the following commands and attach it to the github release: ```bash git clone --branch @POLYBAR_VERSION@ --recursive git://github.com/polybar/polybar.git