We distinguish micro, minor and macro <\/a>releases.<\/p>\n The macro ones are normally fundamental changes to the product. These could be brand-new features that change the way the product serves the user or a complete overhaul of the user interface<\/a>.<\/p>\n The minor releases involve incremental improvements to the product that make it better but don’t dramatically change the way users engage with the product. These kinds of releases are the key to product growth.<\/p>\n Finally, the micro releases included tweaks meant to fix bugs. Unless they’re extremely urgent, these are normally delivered and shipped in batches.<\/p>\n Who writes release notes normally depends on the size of the company.<\/p>\n In a small start-up, this job could belong to the lead developer, while in a larger business it could be the responsibility of the product manager or product owner<\/a>. In really large companies, writing software release notes can be a collaborative task involving product managers<\/a>, the head of product, or the chief product officer.<\/p>\n The marketing <\/a>or customer success manager<\/a> may also play a role, for example, in distributing release notes. This is to make sure that customers know about updates and improvements to the product that will change the way they use the product.<\/p>\n <\/p>\n <\/p>\n <\/p>\n![\"Release](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/02\/release-notes-best-practices-number_ac022d561f0e95ac414d6226e9dd8254_800.webp)
<\/picture>Who is responsible for writing release notes?<\/h2>\n