Slowing down releases: fewer, bigger, less noisy

[piwi3910]

I want to change how I've been shipping procoder.

Up until now I've released fast — often a tag per bug fix or per feature, sometimes several in a single day. On 20 August alone there were 13 releases. That pace was useful while the foundations were still moving fast, but it's not something I want to ask anyone to keep up with. Nobody should have to update their binary or plugin multiple times a day just to stay current.

From now on, I'm going to slow the release cadence down deliberately. Instead of tagging the moment one thing lands, I'll let work accumulate and bundle it into a single, bigger release. Fixes, features, and docs changes will still land in main continuously — you'll see them in commits and PRs as always — but the tags, the binaries, and the changelog entries will come less often and carry more with them each time.

The goal is simple: fewer interruptions for you, less "did I miss a release" fatigue, and release notes that are actually worth reading because they cover real, meaningful chunks of work rather than a single line.

Nothing about how I build changes — small, deliberate commits, one thing at a time, still gated the same way. What changes is only when I decide a set of them is ready to call a release.

Thanks for following along — and if the slower cadence ever gets in the way of something you need sooner, say so here.