m (internal link cleaning) |
|||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
This is a [[:Category:Marketing SOPs|Marketing SOP]] that describes how to write a final announcement for a Fedora operating system release. | This is a [[:Category:Marketing SOPs|Marketing SOP]] that describes how to write a final announcement for a Fedora operating system release. | ||
According to the [http:// | According to the [http://fedorapeople.org/groups/schedule/ task schedule] for upcoming version, 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. | 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 [ | Items for the [[Release_announcements#Process|Release announcement process]] need to be moved over to here. | ||
== Examples == | == Examples == | ||
| Line 20: | Line 18: | ||
Gather information on this upcoming release and its features. | Gather information on this upcoming release and its features. | ||
* Read the [ | * Read the [[Docs/Beats|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. | ||
* Check out the [ | * Check out the [[FWN|Fedora Weekly News]] | ||
* Recycle Alpha and Beta release notes. | |||
* Alpha and Beta reviews also give insight on what Fedora users like. | * Alpha and Beta reviews also give insight on what Fedora users like. | ||
* Interview those who worked on the new features in this release. | * Interview those who worked on the new features in this release. | ||
* Review the [http://fedoraproject.org/wiki/ | * Review the [http://fedoraproject.org/wiki/Fedora_{{FedoraVersionNumber|next}}_talking_points talking points.] | ||
=== Step 2 === | === Step 2 === | ||
Start writing on the wiki | [[F{{FedoraVersionNumber|next}} release announcement|Start writing on the wiki]] | ||
Thank the developers, porters, project leaders, Fedora contributers, and Red Hat employees who made the features possible. | Thank the developers, porters, project leaders, Fedora contributers, and Red Hat employees who made the features possible. | ||
| Line 35: | Line 33: | ||
=== Step 3 === | === 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. | 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 === | === Step 4 === | ||
| Line 44: | Line 42: | ||
Release on release date. Celebrate a fresh Fedora. | 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 == | == Templates == | ||
=== Template 1 === | === Template 1 === | ||
[[Final announcement template]] is based on Fedora 13's announcement. | [[Final announcement template]] is based on Fedora 13's announcement. | ||
Latest revision as of 20:49, 19 September 2016
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 for upcoming version, 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.
- 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.
- Check out the Fedora Weekly News
- Recycle Alpha and Beta release notes.
- Alpha and Beta reviews also give insight on what Fedora users like.
- Interview those who worked on the new features in this release.
- Review the talking points.
Step 2
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.