A few hot-air balloons rising slowly over a wide valley of soft rolling hills at sunrise, a calm river winding along the

[Product] [X.Y]: [Headline]

Released [date] · [platforms] · [who gets it]

Writing tips

Write for the people who use it. Say what they can now do, not what the team did: “You can now export a whole folder as PDF from the Share menu”, not “Implemented batch PDF export (PRJ-1142)”.

Lead with what most people will notice. Order every section by how many people it affects.

Describe fixes as people saw the problem, so they recognise it: “Pasting a large table no longer closes the app.”

Delete any section with nothing in it, Before you update included, and this panel, before you publish.

What this release means for the people who use it, in two or three sentences.

Before you update

Backups, minimum versions, moved settings, removed features.

Highlights

[Biggest change]

Screenshot or short video

New

Improved

Fixed

Known issues

With the workaround, and when a fix is due.

Questions or feedback:

All releases: