Release Notes & Changelog

A public changelog people actually read, a style guide and entry template, a weekly publishing routine with accuracy checks, and the notices, digests and developer feeds that tell customers what changed and what to do.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Release Notes & Changelog, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Release Notes & Changelog

Writing clear release notes and a public changelog that tell customers what changed, why it matters and what they need to do.

  1. Audit of the last six months of release notes
  2. Release notes reader map by audience
  3. Ownership and sign-off rules for release notes
  4. Deciding where the public changelog lives
  5. Release notes style guide
  6. Change categories and labels for every entry
  7. Standard release note entry template
  8. Release note flag on tickets at planning time
  9. Version and date convention for changelog entries
  10. Weekly changelog publishing routine
  11. Accuracy review before a note goes out
  12. Monthly product update email to customers
  13. Internal release briefing for support and sales
  14. Public known issues page kept in step with fixes
  15. Release notes pipeline from merge to publish
  16. Quarterly changelog archive tidy
  17. Release notes reach and usefulness metrics
  18. Reader questions and confusion log
  19. Benefit-led release note headlines practice
  20. Plain language for technical changes
  21. Bug fix notes customers recognise
  22. Writing action-required and breaking change notices
  23. Screenshots and short clips that stay current
  24. Studying ten changelogs people actually read
  25. Drafting notes from commits and tickets
  26. In-app what's new panel decision
  27. Labelling notes by plan, role and rollout stage
  28. Changelog subscriptions by email, RSS and feed
  29. Rewriting vague past entries
  30. Linking every note to updated help articles
  31. Corrections policy for published notes
  32. Accessibility check of the changelog page
  33. Public changelog launch with three months back-filled
  34. Major version release notes and upgrade guide
  35. Product year in review post
  36. Release note for a pricing or plan change
  37. Emergency hotfix note within the hour
  38. Release notes for a redesign that moves things
  39. Thirty-minute weekly changelog for a solo founder
  40. Customer update notes for a small business app or online shop
  41. Sprint release summaries for agency clients
  42. What gets a note under continuous deployment
  43. Enterprise admin release notes with advance notice
  44. Handing over release notes to a new owner
  45. Developer changelog for an API or SDK
  46. Security fix wording and advisories
  47. Translated release notes for key languages
  48. Change records for customers who audit your releases
  49. Single-source changelog feeding every channel
  50. Changelog entries reused for marketing and sales

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Audit of the last six months of release notes

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most teams discover their release notes are scattered across a help centre page, a few emails, some in-app pop-ups and a Slack channel only staff can see.

First tasks

  • List every channel where release notes have gone out since six months ago
  • Export the completed tickets or merged pull requests for the same period
  • Mark each shipped change as announced, announced late or never announced
  • Ask the agent to summarise the recurring wording problems in one page

Release notes reader map by audience

Release notes are read by end users scanning for something they asked for, admins checking whether anything will break, developers looking for API changes and your own support and sales staff preparing for questions. Writing one note for all of them usually satisfies none.

First tasks

  • Ask support which release questions customers raised most last quarter
  • List the reader groups and the channel each one actually checks
  • Rank the groups by the damage done when they miss a change
  • Refresh the reader map against the current customer mix @recurring(yearly)

Ownership and sign-off rules for release notes

When nobody owns release notes, they are written at the last minute by whoever merged the code, or not at all. Agreeing who drafts, who checks the facts, who approves sensitive wording and who presses publish removes the Friday afternoon scramble. It also gives engineers a clear answer to the question of what they owe the note.

First tasks

  • Name the changelog owner and a backup for holidays and sick days
  • Write a table of who drafts, checks, approves and publishes
  • List the change types that need legal, security or finance sign-off
  • Confirm the owner and sign-off table still match the team @recurring(yearly)

Make it yours.

Install Release Notes & Changelog, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.