From Fedora Project Wiki
| Line 29: | Line 29: | ||
# Is your package included in the default install of one of the main spins? | # Is your package included in the default install of one of the main spins? | ||
# Is your package ''the'' default application of | # Is your package ''the'' default application of its type? | ||
# Is your package involved in the building of the entire distro? For example, rpm, gcc, glibc, etc. | # Is your package involved in the building of the entire distro? For example, rpm, gcc, glibc, etc. | ||
# Are there a large number of packages that depend on your package that will be effected by an upgrade/change/etc ? | # Are there a large number of packages that depend on your package that will be effected by an upgrade/change/etc ? | ||
Revision as of 16:07, 12 March 2010
Enhancements
Enhancements are:
- Less documented improvements to a Fedora release which do follow the feature process and do not fit the feature definition below.
- Added to the release summary by anyone under heading of Other Enhancements. The release summary for each release lives in the following namespace: http://fedoraproject.org/wiki/Releases/<release number>/ReleaseSummary
Features
Definition of a Feature
A feature is defined as a significant change or enhancement to the version of Fedora currently under development that may or may not include new packages.
Features are usually considered to meet one or more of the following objectives:
- highly user visible changes (beyond artwork or theme changes)
- improvements or changes that require non-trivial cross-package integration
- exciting new capabilities we can trumpet fedora having--some of this is good public relations. Some examples might include:
- work Fedora contributors are doing upstream as part of their work for Fedora
- new features from upstream that we are making available in the Fedora for the first time
- improvements that are Fedora specific. Example from past releases include the Core and Extras Merge and smolt
- significant enough that if not completed properly or without a proper backup plan could delay the release
- noteworthy enough to call out in the release notes
Still Not Sure?
Start with this checklist:
- Is your package included in the default install of one of the main spins?
- Is your package the default application of its type?
- Is your package involved in the building of the entire distro? For example, rpm, gcc, glibc, etc.
- Are there a large number of packages that depend on your package that will be effected by an upgrade/change/etc ?
- Are you trying to promote this package as a Feature for publicity reasons?
- Does your package enable something that is highly end-user visible. For example, magically working wireless, push button pony making, etc.
If yes to any of the above, please create a Feature page. If no, or you are still unsure, ask one of your FESCo representatives and they will guide you.