Bug 240815 - Need release announcement for F7
Summary: Need release announcement for F7
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes
Version: devel
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Karsten Wade
QA Contact: Karsten Wade
Depends On:
Blocks: fc-relnotes-traqr
TreeView+ depends on / blocked
Reported: 2007-05-21 21:38 UTC by Jesse Keating
Modified: 2013-01-10 02:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-09-28 21:46:11 UTC

Attachments (Terms of Use)

Description Jesse Keating 2007-05-21 21:38:00 UTC
We need a release announcement for Fedora 7.

Comment 1 Karsten Wade 2007-05-22 06:17:31 UTC

That needs to be fleshed out.  Can you put in any relevant and salient points in
that page?  We need to finish this soon, to give the Ambassadors et al a chance
to build their announcements from the TalkingPoints.

It could/should draw from:


Once we have the TalkingPoints settled, then it is easy to write up a snappy
announcement in en-US.

Comment 2 Karsten Wade 2007-05-26 00:07:06 UTC

Can you or anyone who knows all the particulars help us to fill out the "Where
to get" details in the release announcement template?


I'm going to put in particulars from past announcements, but will leave out the
download details.

Comment 3 Karsten Wade 2007-05-26 00:31:34 UTC
After looking at the FC-6 announcement, as compared to the others, and I
realized we may not have much in terms of template.  What do you think, oh
release engineer types?  Is less truly more?


Comment 4 Karsten Wade 2007-05-29 01:14:50 UTC
OK, Paul and I have worked out an idea for the announcement.  I'm working to
finish the talking points by tonight.  We'll have something ready for ya.  

Jesse -- Reminder to confirm that we have enough content in our
AnnouncementTemplate that pertains to release details (torrent, URLs, etc.) (see
comment #2)

Comment 5 Jesse Keating 2007-09-28 21:46:11 UTC
This was obviously done.

Note You need to log in before you can comment on or make changes to this bug.