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

Re: Frozen feature list for FC7

On Tue, 2007-03-06 at 17:43 -0800, Peter Gordon wrote: 
> On Tue, 2007-03-06 at 20:08 -0500, Warren Togami wrote:
> > Features have not historically been tracked formally in Fedora. 
> > Features just would sort of land if they were completed before freeze 
> > dates.  I suppose we could improve this in the future, but is the Wiki 
> > really the best way to represent this?
> Hence the 'fedora_requires_release_note' Bugzilla flag? :)
> Is there a formal policy for that like there is for the fedora-cvs one?
> If not, then we could simply request that flag ('?') and add a note to
> the package's review request (or another resolved RFE bug) stating the
> cool new significant feature that has been added/changes. Then perhaps
> this can go to the fedora-docs list and someone can approve ('+') the
> flag when this is added or deny it ('-') with a brief explanation as to
> the reasoning for its denial.

I think you have to set the flag to '+' to trigger it, right?  At that
point, we can ACK it in a comment and point to where the content went.
Not including the content should definitely get a '-'.

Added now at:


Note that all of these methods of filing a release note are piped into
relnotes fedoraproject org   That is then fed into a mailman list
(fedora-relnotes-content) that is the "firehose of raw release

> Also, the Docs/Beats on the wiki are writable to all Fedora Account
> holders, right? Could setting the flag in Bugzilla automagically add
> that note the wiki if the flag requester has a Fedora account/is in the
> EditGroup?

That is an interesting idea.  We'd have to have a way of identifying
which beat should receive the content; it seems doable.  Best thing to
do with this idea is to file an RFE in bugzilla against the release

thx - 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]