Release announcements

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(strawman schedule, fixing formatting, linking to F9 announcement as an example)
Line 16: Line 16:
 
== Past Release Announcements ==
 
== Past Release Announcements ==
  
 +
* [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-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/2007-May/msg00009.html F-7]  
Line 30: Line 31:
 
== Process ==
 
== Process ==
  
1. A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of [[Releases/TalkingPoints| talking points]] .
+
# A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of [[Releases/TalkingPoints| talking points]] .
1. A [[Releases/9/Announcements/AnnouncementTemplate| 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.
+
# A [[Releases/9/Announcements/AnnouncementTemplate| 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 [[Releases/9/Announcements/AnnouncementTemplate| template page]]  and paste in to a plain text editor so it removes all formatting from the HTML/wiki.
+
#* To use the template, copy the content from the [[Releases/9/Announcements/AnnouncementTemplate| template page]]  and paste in to a plain text editor so it removes all formatting from the HTML/wiki.
1. 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.
1. Drafts can be worked on [[Releases/9/Announcements| here on the Wiki]] , via direct email, or whatever method the collaborators choose.
+
# Drafts can be worked on [[Releases/9/Announcements| here on the Wiki]] , via direct email, or whatever method the collaborators choose.
1. 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
* Any Fedora contributor who reads the language is an eligible editor.
+
#* Any Fedora contributor who reads the language is an eligible editor.
1. 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.
+
# 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.
  
<!-- These steps are removed for F9 due to timing, and moved out of line because the comments break the numbering.
+
== F10 Announcements Schedule ==
-->
+
<!-- 1. Each language draft is due for review after the final test release (usually test3, occasionally test4.)
+
-->
+
<!-- 1. Final versions are created during the time between the final test and release
+
-->
+
  
{{Anchor|Schedule}}
+
''Strawman schedule to cover us just-in-case; needs to have longer lead times. [[User:Kwade|quaid]] 03:17, 25 September 2008 (UTC)''
== F9 Announcements Schedule ==
+
  
 
{| style="t1" rowclass="th"
 
{| style="t1" rowclass="th"
 
|-
 
|-
| 7 May || Talking points ready
+
| 19 Nov || Talking points ready
 
|-
 
|-
| 9 May || First drafts of all release announcements
+
| 21 Nov || First drafts of all release announcements
 
|-
 
|-
| 11 May || Final English release announcement ready
+
| 23 Nov || Final English release announcement ready
 
|-
 
|-
| 12 May || All release announcements ready
+
| 24 Nov || All release announcements ready
 
|-
 
|-
| 13 May || Release the announcements!
+
| 25 Nov || Release the announcements!

Revision as of 03:17, 25 September 2008

Contents

Release Announcements

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 namespace where regional and/or language-specific groups can work on their truly localized version of the release announcement for Fedora.

An important part of this is writing up the talking points . Refer also to Releases/Announcements/TalkingPoints , a page that explains more about how to use the talking points.


Past Release Announcements

(And now you know why we don't let Bill write them anymore!)

Process

  1. A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of talking points .
  2. A 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 template page and paste in to a plain text editor so it removes all formatting from the HTML/wiki.
  3. Any local group wanting to write a native-language Fedora release announcement needs to form a group of 2 or more collaborators.
  4. Drafts can be worked on here on the Wiki , via direct email, or whatever method the collaborators choose.
  5. 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.
  6. 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

Strawman schedule to cover us just-in-case; needs to have longer lead times. quaid 03:17, 25 September 2008 (UTC)

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!