Final announcement SOP

From FedoraProject

Revision as of 09:48, 30 November 2012 by Jreznik (Talk | contribs)

Jump to: navigation, search
Note.png
This SOP is not complete!
If you have time, please write this SOP by looking at the Fedora 13 announcement and filling in notes on how to create the F14 deliverable.

Contents

Introduction

This is a Marketing SOP that describes how to write a final announcement for a Fedora operating system release. According to the task schedule, the release announcement must be ready to occur on release day. Work on the announcement can begin at any time but its peak window of productivity is 17 days prior to release. It should be complete by a week before the operating system release.

Note: The purpose of the release announcement is to let the community know how awesome this release is to encourage download and installation. The release notes are a separate more extensive document to be a reference for those who have installed.

Items for the Release announcement process need to be moved over to here.

Examples

You can see examples of past final release announcements at Final announcement.

Instructions

Step 1

Gather information on this upcoming release and its features.

Step 2

Start writing on the wiki

Thank the developers, porters, project leaders, Fedora contributers, and Red Hat employees who made the features possible.

Step 3

Proofread. Discussion on the Fedora marketing list will follow with release announcement candidates. Being open at this stage in the process will reduce last-second edits later. Contact Feature Wrangler for review to make sure announced Features were delivered in the final release.

Step 4

Attend the release readiness meeting. This is last call for changes.

Step 5

Release on release date. Celebrate a fresh Fedora.

Final announcement is sent by Fedora Project Leader (FPL) to (at least) Fedora announce, devel-announce and test-announce mailing lists.

Templates

Template 1

Final announcement template is based on Fedora 13's announcement.

Template 2

Improve this SOP!

If you see a way to improve this SOP, please go ahead and edit the page - you don't need to ask for anyone's permission. Read more about our contribution philosophy here.