This gives some information on how a release announcement should be formulated, how screenshots should look and what information needs to be in there.
See the openSUSE Product Highlights writing guide, it was essentially build on how we do stuff.
A release announcement informs the press, our users and the outside world about a release. See kde.org/announcements for some examples.
Writing an announcement happens in three stages, with different people and skills involved.
We gather data as soon as we can. We ask developers and others regularly to note major/noteworthy features on a etherpad on notes.kde.org. We also gather link to blogs etc. and sometimes digg through commit digests and mailing lists.
This step is crucial: we can easily miss things so we need help from the developers and others in our community!
While phase one is being worked on (adding info) some writers can start turning the rough notes into proper text. That means making a short intro to each main section, further dividing it up and turning the bullet points and pasted text into real, consistent text suitable for publication.
See older announcements for guidelines on how to write. In general, gather related things as much as you can - find common themes for example. Link to the original blog posts and don't be TOO wordy ;-)
The last phase is to fill in the final details. Once the text is considered complete, it needs to be reviewed for good English, and most importantly, the 'techy folks' need to review the document, and ensure that facts are correct, nothing has been omitted and everything is up to date.
We need a summary on top, proper paragraphs, stuff like that. And last of all are the bells and whistles - images and videos to create a rich user experience.
... but it isn't out yet. Next is putting the text on the dot, preparing mails for the press and our announce mailing list, getting the changes on kde.org done etcetera. The release team maintain a release checklist here.
All screen shots must be taken as follows: