@fortuna Sure. it begins by pausing for a moment and reflecting on what the release contains. Making the pause happen is the hard part since developers don't tend to want to pause. Until we get that pause and the moment of reflection there's no practical way to make it better.
@craigmaloney I believe that works well for single-person or small project but it's challenging when you need to scale to many changes and collaborators.
In that case release notes will scale better if you maintain running notes, updated when important changes happen by the authors themselves.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!