Beta announcement SOP
This is a Marketing SOP that describes how to write a beta announcement for a Fedora operating system release. According to the task schedule for upcoming version, the beta 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 the beta release. It should be complete by a week before the operating system beta 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.
You can see examples of past beta release announcements at Beta announcement.
Gather information on this upcoming beta release and its features.
- Read the beats and look for features that excite you. Note, some Beats are committed to git://git.fedorahosted.org/docs/release-notes.git as they are written.
- Read Features List
- Recycle Alpha release notes.
- Alpha reviews also give insight on what Fedora users like.
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 beta release.
Attend the beta release readiness meeting. This is last call for changes.
Release on beta release date.
Beta announcement is usually sent by Release Engineering or Program Manager to (at least) Fedora announce, devel-announce and test-announce mailing lists.
Beta announcement template is based on Fedora 13's announcement.
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.