John,
I would like to propose the following changes to the Release Notes
schedule. Rudi is taking point on the Guides part of the schedule:
Add to alpha
Validate former beat writers
10 days before "Start Alpha Beat and Feature page Review"
Elapsed time 5 days
note "Check that beat writers for previous release are willing
to contribute to the current release"
Recruit new beat writers
After "Validate Beat Writers"
Elapsed time 5 days
note "Identify unmanned beats and recruit contributors to
handle those beats"
Notify Devel alpha release notes
5 days before "Comb Beats and Feature Pages for Alpha"
Elapsed time 0
note "Send notification to devel list that work on alpha release
notes is starting and developers wishing to be mentioned should
consider commenting in the appropriate beat as well as having
feature page complete"
Beta changes
"Port Wiki to Publican"
should extend one day past "Wiki Freeze"
"Reminder to development: wiki freeze in 7 days"
Should be part of GA release notes, not beta
"Build and post release-notes to docs.fedorahosted.org"
Change description to:
"Build and post beta release notes to docs.fedoraproject.org"
Add "Build and post Fedora Technical Notes to docs.fp.o"
Same date as "Build and post beta release notes to
docs.fedoraproject.org"
Change description "Build fed-rel-notes.rpm for Beta Release" to
"Build f-r-n.rpm and push to updates-candidate"
note "fedora-release-notes.rpm needed for nightly compose"
GA Changes
add "Update and post Fedora Technical Notes to docs.fp.o"
Same date as "Final (GA) Release"
Thanks
--McD
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
