Features/Policy: Difference between revisions
No edit summary |
|||
| Line 86: | Line 86: | ||
== How does a feature get accepted? == | == How does a feature get accepted? == | ||
Acceptance by the | Acceptance by the Release Manger is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release. | ||
Feature acceptance is agreement by the | Feature acceptance is agreement by the Release Manager that a particular feature is supported by the community: | ||
# consistent with the goals and policies of Sugar | # consistent with the goals and policies of Sugar | ||
# supported by the Sugar | # supported by the Sugar community | ||
# suitable for listing as an Official Feature of the next release of Sugar | # suitable for listing as an Official Feature of the next release of Sugar | ||
# important to track prior to feature freeze and could affect timeliness of release | # important to track prior to feature freeze and could affect timeliness of release | ||