Release threads

meta
1

Having these release threads is nice, but to be honest sometimes they feel quite noisy to me. For example, currently out of 20 most recently updates threads, 16 are release ones. I was thinking that maybe it would be better to have one thread per gem or one per gem and major version, and the release bot finding the relevant existing thread and posting update to it.

As a disclaimer, I haven’t checked the implementation and how hard it could be. Just starting a discussion.

2

I second this as I’m exhausted by the duplication as well. Case in point, I recently complained to Javier – who runs the Ruby Users Forum – to stop allowing Hanami updates (but not just Hanami, other projects as well).

We already have powerful solution for this: RSS. Thankfully, Hanakai’s feed is auto-discoverable via your feed reader through this link in the head of the DOM: Hanakai . Only a single feed is all we need (or a feed per project – as you mentioned – so folks can pick and choose as best fits their workflow).

:bulb: This is what I do for all of my projects where each project has it’s own feed! Everything is automated using the Milestoner gem which, by the way, is built atop Hanami View which means you can completely customize all templates to render however you like in multiple formats: HTML, Markdown, ASCII Doc, RSS, etc.

3

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
1 Like
4

One thread for all Hanami sounds even better (if it’s possible), because indeed they are usually released in batches :+1: