policy question

[Rahul Sundaram]

Beartooth wrote:
> 	Can anybody explain to a non-technoid how the developers go about 
> deciding whether a new thing gets added to the current Fedora release, or 
> held to become part of the next?

Can you explain what you mean by a "new thing"? Do you mean a new 
software package or new feature or something else?

New packages go through a peer review process described in

http://fedoraproject.org/wiki/Package_Review_Process

They should in minimum pass the MUST requirements

http://fedoraproject.org/wiki/Packaging/ReviewGuidelines

Major features before a new release go through a feature process 
described in

http://fedoraproject.org/wiki/Features/Policy

A release is done as per the release criteria

http://fedoraproject.org/wiki/QA#Release_Testing

Individual features have to go through the testing plan and if that 
fails would be postponed to the next release. One example here is 
swfdec, a free and open source flash player that was installed in the 
Fedora 9 beta and removed in the final release because it failed the 
criteria set in

https://fedoraproject.org/wiki/QA/TestResults/Fedora9Swfdec/Rawhide

It is a combination of release schedule set by release engineering, QA 
team determining release critical bugs and Fedora Engineering steering 
committee managing the overall process.

Post release, it is generally the people maintaining the package 
(whether a individual or a team) determines whether it should be made 
available as a update. One recommendation is not to break ABI post release.

https://fedoraproject.org/wiki/PackageMaintainers/PackagingTricks

Rahul