This is good feedback, thank you.
We’ve been through a full cycle of releases (occasional updates over a few months, followed by a full Hanami release), so now’s a great time to step back and review the setup.
I do want to continue to make our releases more discoverable by publishing them into places like this, but I agree that the current implementation is noisy.
I like your suggestion, @katafrakt! My proposal, then:
- As you’ve suggested, one topic per gem per
<major>.<minor>release. The smaller non-breaking releases would be attached as additional posts on that topic. - And a special approach for Hanami. One thread per
<major>.<minor>release for the whole framework. This would require a manual posting for the initial release (aggregating all the changelogs), but then non-breaking updates could be added to the topic via our release automation.
How does that sound?
This will require changes to release-machine/.github/scripts/announce-to-forum.rb at main · hanakai-rb/release-machine · GitHub. I can aim to get this sorted out before the next Hanami releases, since I think those are the biggest source of noise.
I can also do some manual cleanup of the existing Hanami release topics sometime soon.
If the releases category is still too much noise for some, Discourse fortunately gives you some options:
- You can mute the category, by clicking the bell icon and selecting “Muted”.
- If you still want the updates but would rather consume them in another way, our categories here have their own RSS feeds. Here’s the feed for releases:
https://discourse.hanakai.org/c/releases/17.rss