←back to thread

How to Write Compelling Release Announcements

(refactoringenglish.com)
69 points mtlynch | 2 comments | 25 Jun 25 14:22 UTC | HN request time: 0.833s | source
1. continuational ◴[25 Jun 25 14:48 UTC] No.44377990[source]▶
Also: Please don't announce it as "Thingie 3.5.27". That title says nothing about what's new or interesting about this release.
replies(1): >>44378928 #
2. miningape ◴[25 Jun 25 16:12 UTC] No.44378928[source]▶
It actually does, specifically it indicates the degree to which something has changed - importantly, if action is required on the user's end (breaking releases). Or if there have been significant changes or a milestone was released (e.g. 1.0.0 means it's stable for production)

As a developer I can tell at a glance how much work this will take and whether to escalate it.

That being said I'm not opposed to a bit more detail "Thingy 3.12.10 - Miraculous Monitoring Metrics". And also I don't see a point in non-technically focussed products using this style either.

https://semver.org/