Writing GNOME release notes
Note: This refers to 3.2 (to be released by the end of September 2011) and is still subject to change.
Send an announcement email asking people to provide information (potential recipients: desktop-devel-list, marketing-list, gnome-accessibility-list, gnome-doc-list, gnome-i18n, release-team)
Ask specific questions on the marketing-list if needed (for 3.2 this was needed for Featured Apps story)
- After sending the announcement email, give developers a few days to edit the wikipage.
Branch release-notes in GNOME Git for gnome-3-x (see Branching)
Ask FredericPeters to set up http://library.gnome.org/misc/release-notes/3.x/ and password protection, once the skeleton has been committed. While working on the release notes this will make it easier to see recent changes and its design.
Take a look at a potentially already existing Release Notes wikipage for this release and clean it up if needed
Also go through the Commit Digests of the last months to find more interesting stuff to mention
- Documentation: Ask Docs Team/ShaunMcCance for any new user docs and for docs converted from Docbook to Mallard format
Go to Damned Lies, take alphabetic list of all languages with more than 70% (safe, as you can still comment languages later that didn't reach 80%), and add them in the format of <listitem><para>LanguageName</para></listitem>.
Text in good shape but needs some more tweaking
Text basically finished
Let somebody proof-read for content and for spelling+grammer.
For content: Someone from the design team (e.g. William Jon McCann). Spelling+grammer: someone from documentation team (e.g. Shaun McCance)
Get listed on http://l10n.gnome.org/module/release-notes/
Close to the release
Add comment markers to those languages in rni18n.xml that did not reach at least 80% on http://l10n.gnome.org/releases/gnome-3-2/
- Celebrate the release
In this specific case it refers to version 3.4
- Use Mallard instead of Docbook format