[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

bz relnotes flag



Today a new flag was added to bugzilla for Fedora components.  By
flipping the 'fedora_requires_release_notes' flag, the release notes
team is alerted that the something in this bug report is worth tracking
in the release notes.[1]

The release notes process has now been updated to reflect the "Six Ways
to Submit a Release Note":

http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process

Six Ways to Submit a Release Note
These are in order of preference, starting with the best option: 

     1. Edit the content directly within the appropriate beat at
        http://fedoraproject.org/wiki/Docs/Beats. 
        
     2. Email relnotes fedoraproject org  
        
     3. Add relnotes fedoraproject org as a Cc: in an existing bug
        report. 
        
     4. Change the fedora_requires_release_note flag on an existing
        Bugzilla entry to '+' (NEW) 
        
     5. Enter a new release note request, comment, etc. into this
        pre-filled bugzilla request (http://tinyurl.com/nej3u).
        
     6. Include the *docs* keyword in your CVS commit log. 

[1] Kudos to Uli Drepper for finding and using this flag within three
hours of it being added; thanks to Dave Lawrence for coming out of
retirement to add the flag.

- 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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]