How To Contribute to the Release Notes

This page is where we explain how-to use this Wiki for writing release notes beats.


 * 1) Find the appropriate beat, such as  Docs/Beats/Desktop, and edit your content into the page.  There is a list of existing beats at Documentation Beats.
 * 2) If the page does not exist, create a new one, either at the top-level or as a sub-page, in the format of  Docs/Beats/Beatname .  Edit the main page at  Docs/Beats  to add it to the table of contents.
 * 3) Don't worry. Competent writers and editors are watching your contributions.  We'll follow up with your contribution directly in the Wiki, cleaning, simplifying, formatting, and so forth.

For more details, read on:

You need to be a recipient of email to relnotes@fedoraproject.org. This is a manual alias (for now), email kwade@redhat.com to be added. This address receives all bug reports assigned to relnotes@ (including the release-notes component in bugzilla), and all CVS commits that contain the  keyword in the log message.

Read and understand about the release notes beats.

Keep to the Schedule
The documentation schedule  for Fedora includes time for translation of content so that it all can be included within the ISOs.

Release notes are an ongoing process, with rolling releases throughout testing and after final release.

Gathering Raw Notes and Using the Wiki
Beat writers are now able to use the tree at Docs/Beats  to gather raw input and form it into content for the release notes.

These pages have a light structure that generally goes one layer deep, for example, Docs/Beats/Kernel  is for the kernel portion of the release notes.

Beat writers are free to add and change sub-pages, as they need. Other contributors can do the same. The only requirement to edit is that the user be registered and logged in.

Wiki-help for beat contributions is now on-topic for #fedora-docs.

Keeping a Relevant Beat
Beat writers need to keep the content cleaned-up and relevant. You want to watch your page and all sub-pages using the pattern  in your "Subscribed wiki pages" of your UserPreferences.

Snapshots and Changes
These beat notes are ongoing workspaces. A snapshot is taken just prior to freeze for translation, and the content is merged into the overall DocBook/XML-based release notes, as per the FDP release schedule.

Beat writers need to keep the content cleaned-up and relevant. You want to watch the Docs/Beats/Beatname* pages for all changes.

Another snapshot may be taken one or two days before release, to capture any new content that came after the translation freeze snapsot. This secondary snapshot is used to create a latest release notes that is linked from the as-shipped release notes. This latest relnotes is published online at a fixed URL, and helps to make up for the loss of content that appeared or was changed after translation freeze.