anon is not alone

release management

I manage releases for a bunch of free & open-source software. Just about every time I ship a release, I find a novel way to fuck it up. Enough of these fuck-ups have accumulated now that I wanted to share some of my mistakes and how I (try to) prevent them from happening twice.

I’ve only done some internal software release management at a prior job, a task that was partially manual and error prone (at least when I was doing it). It feels surprisingly good to read about others failures, especially when the author himself is a fairly well-known and respected maintainer.

(link to source)