From Fedora Project Wiki
m (Releases/Announcements moved to Release announcements: Proper wiki name) |
(updating content; reorganizating; clarifying; fixing links) |
||
| Line 1: | Line 1: | ||
[[Category:Docs Project]] | [[Category:Docs Project]] [[Category:Marketing]] | ||
An important part of a Fedora release is its announcement. The release team composes a release announcement sent on the day of the release. | An important part of a Fedora release is its announcement. The release team composes a release announcement sent on the day of the release. | ||
Each local team is encouraged to write its own announcement in a way that makes the most sense for the local community. This is a | Each local team is encouraged to write its own announcement in a way that makes the most sense for the local community. This is a truly localized version of the release announcement for Fedora. | ||
An important part of this is writing up the [[ | An important part of this is writing up the [[Release talking points]]. Refer also to [[Release announcement talking points]], a page that explains more about how to use the talking points. | ||
For Fedora 10, use [[Talking points for F10]]. | |||
== Process == | == Process == | ||
# A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of [[ | # A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of [[Release talking pPoints]]. | ||
# A [[ | # A [[Release announcement template]] is produced using structured text in plain ASCII. It includes a block at the top for the local content, then a complete amount of standard boilerplate. | ||
#* To use the template, copy the content from the [[ | #* To use the template, copy the content from the [[Release announcement template]] page and paste in to a plain text editor so it removes all formatting from the HTML/wiki. | ||
# Any local group wanting to write a native-language Fedora release announcement needs to form a group of 2 or more collaborators. | # Any local group wanting to write a native-language Fedora release announcement needs to form a group of 2 or more collaborators. | ||
# Drafts can be worked on | # Drafts can be worked on here on the Wiki, via direct email, or whatever method the collaborators choose. | ||
# The draft must be reviewed and approved by an independent reader of that language. | # The draft must be reviewed and approved by an independent reader of that language. | ||
#* This needs to be someone from outside of the collaboration circle that wrote the draft | #* This needs to be someone from outside of the collaboration circle that wrote the draft | ||
| Line 39: | Line 22: | ||
== F10 Announcements Schedule == | == F10 Announcements Schedule == | ||
{| style="t1" rowclass="th" | {| style="t1" rowclass="th" | ||
| Line 53: | Line 34: | ||
|- | |- | ||
| 25 Nov || Release the announcements! | | 25 Nov || Release the announcements! | ||
== Past Release Announcements == | |||
These give you an idea of how they have been written in the past. | |||
* [http://www.redhat.com/archives/fedora-announce-list/2008-May/msg00007.html F-9] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2007-November/msg00006.html F-8] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2007-May/msg00009.html F-7] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2006-October/msg00008.html FC-6] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2006-March/msg00027.html FC-5] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2005-June/msg00010.html FC-4] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2004-November/msg00002.html FC-3] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2004-May/msg00010.html FC-2] | |||
* [http://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html FC-1] | |||
(And now you know why we don't let Bill write them anymore!) | |||
Revision as of 18:35, 19 November 2008
An important part of a Fedora release is its announcement. The release team composes a release announcement sent on the day of the release.
Each local team is encouraged to write its own announcement in a way that makes the most sense for the local community. This is a truly localized version of the release announcement for Fedora.
An important part of this is writing up the Release talking points. Refer also to Release announcement talking points, a page that explains more about how to use the talking points.
For Fedora 10, use Talking points for F10.
Process
- A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of Release talking pPoints.
- A Release announcement template is produced using structured text in plain ASCII. It includes a block at the top for the local content, then a complete amount of standard boilerplate.
- To use the template, copy the content from the Release announcement template page and paste in to a plain text editor so it removes all formatting from the HTML/wiki.
- Any local group wanting to write a native-language Fedora release announcement needs to form a group of 2 or more collaborators.
- Drafts can be worked on here on the Wiki, via direct email, or whatever method the collaborators choose.
- The draft must be reviewed and approved by an independent reader of that language.
- This needs to be someone from outside of the collaboration circle that wrote the draft
- Any Fedora contributor who reads the language is an eligible editor.
- Formal announcements are sent out to fedora-announce, fedora-list (either the main list or a language-specific one), via blogs, and into various support channels (#fedora, fedoraforum.org, fedoraunity.org et al, etc.), either international or local ones.
F10 Announcements Schedule
| 19 Nov | Talking points ready |
| 21 Nov | First drafts of all release announcements |
| 23 Nov | Final English release announcement ready |
| 24 Nov | All release announcements ready |
| 25 Nov | Release the announcements!
Past Release AnnouncementsThese give you an idea of how they have been written in the past. (And now you know why we don't let Bill write them anymore!) |