Friends:
You are the developers and package maintainers closest to the work and
testing. You are the best people to highlight your project's changes,
successes, and testing needs via the release notes. The earlier we get
content in, the fewer changes by test3; life is happier for the
translators and editors, and for the community, too.
Did you know it is brain-dead simple to submit content?[1]
These are in order of best to least best:
1. Edit the content directly within the appropriate beat at
http://fedoraproject.org/wiki/Docs/Beats.
2. Email relnotes@xxxxxxxxxxxxxxxxxx
3. Add relnotes@xxxxxxxxxxxxxxxxx as a Cc: in an existing bug
report.
4. Enter any release note requests, comments, etc. into this
pre-filled bugzilla request; http://tinyurl.com/33y7bf. (NOTE:
This Bugzilla link is NOT for problems with Fedora software,
only for problems with the release notes themselves.)
5. Include the *docs* keyword in your CVS commit log.
Each of your projects needs to take responsibility to provide continuous
and final content for the release notes. By sharing the load, we
exponentially increase the quality and decrease the work.
[1] http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process#submitting
- Karsten
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
