From Fedora Project Wiki
< User:Jjmcd | Drafts
Fedora 17 Release Notes Schedule
| Due | Item | Desc | Comment |
|---|---|---|---|
| Validate Former Beat Writers | Note to Docs list followed by email to F16 beat writers | ||
| Notify Development About Alpha Release Notes | |||
| Start Alpha Beat and Feature Page Review | |||
| Comb Beats and Feature Pages for Alpha | Go through feature pages merging highlights into beats | Ultimately select the few features to highlight in the one-page of alpha | |
| Recruit New Beat Writers | Recruit new writers for any orphaned beats | Plan is to post requests to dev list, blog. Then email potential candidates for specific beats discovered by mining review requests. Some beats may be tame enough, or have no features, so they may be left vacant. | |
| Fedora 17 Alpha Release Readiness Meeting | |||
| Prepare Alpha Release Notes (1 page) | Create single page release notes for alpha | ||
| Create Alpha Announcement (Marketing & Docs) | |||
| Post Alpha Release Notes One-Page | |||
| Alpha Public Availability | |||
| Write Unclaimed Wiki Beats | Perhaps a beta release notes party? | ||
| Remind Translation: Beta Rel Notes POT Coming | |||
| Remind announce-list & f-devel-announce: Wiki Freeze | Wiki freeze for beta is Mar 12. Remind Dev the window is closing | Invariably, some developer or another is disappointed that nothing about his app made in into the release notes and the wiki froze by surprise. | |
| Reminder to Trans that new POT files are coming for all guides | |||
| Wiki Freeze: Beta Release Notes | |||
| Port Wiki to Publican | This will probably be mostly scripted. Later conversions will be mostly manual, but this first conversion generally benefits from the automation. | ||
| Start nightly POT files all fed-rel-notes.rpm content | |||
| Ongoing build translation review htmls | |||
| Translation Deadline: Beta Release Notes (PO Files complete) | |||
| Reminder to Trans that Final Guides POT files are coming | On Apr 9, last POTs will go to L10N so no more source updates | ||
| Beta Change Deadline | |||
| Features 100% Complete Deadline | |||
| Build f-r-n.rpm and Push to updates-candidate | Needed some time before docs.fp.o so ready for beta compose | ||
| Reminder: Send Project Wide-Final Release Notes Deadlines | |||
| Fedora 17 Beta Release Readiness Meeting | |||
| Generate nightly POT files all fed-rel-notes.rpm content | |||
| Create Beta Announcement (Docs & Marketing) | |||
| Reminder to Development: Wiki Freeze in 7 days | |||
| Build and Post Beta release-notes to docs.fedoraproject.org | |||
| Build and Post Fedora Technical Notes to docs.fedoraproject.org | |||
| Beta Release Public Availability | |||
| Prepare GA Release Notes | |||
| String Freeze: GA Release Notes | |||
| Remind Translation: RPM Freeze (no more POTs) in 5 days | |||
| Port diff wiki content to Publican | |||
| Generate GA Release Notes POT files for Translation | |||
| Remind Translators of GA Release Notes Deadline in 4 days | Apr 23 we will begin building the release RPM so any translations not ready by then will not make it to GA | ||
| Review and correct GA Release Notes (daily builds html) | |||
| Build GA release note htmls for Translation | Most likely this is a continuation. Drafts should have been being build automatically on a regular basis | ||
| Build fedora-release-notes.rpm | |||
| Create GA Announcement (Docs & Marketing) | |||
| Fedora 17 Final Go/No-Go Meeting (17:00 US Eeastern) | |||
| Fedora 17 Final Release Readiness Meeting | |||
| 0-Day rel-notes build updated rpm | |||
| 0-Day rel-notes update docs.fp.org | Get any changes that did not make it to GA on the the website | ||
| 0-Day rel-notes generate POT | |||
| Add translated zero-day updates to docs.fp.org | |||
| Update redirect | make d.fp.o/release-notes point to en-US/Fedora/17/html/Release_Notes/index.html. | ssh bastion, puppet01, cd puppet/modules/fedora-docs/files, git pull, emacs redirects.conf, commit, push | |
| Final (GA) Release | |||
| Update and post Fedora Technical Notes to docs.fedoraproject.org | |||
| Push updated rel-notes RPMs to Updates repo | |||
A reminder to beat writers ...
The conversion to XML will be easier if the original wiki is marked appropriately:
Package names should be marked as packagename
File and directories should be marked as /dir/name
Commands should NOT be indented. e.g.:
yum check-update
gui menus and items should be marked About Me
Keystrokes [Key]
In general, you want to start discussion of a new package with a new subsection:
postgresql
None of these are cast in bronze, but following these guidelines will make the conversion to XML a lot easier.