Changes

569 bytes added ,  06:39, 30 June 2009
Line 77: Line 77:     
== How does a feature get accepted? ==
 
== How does a feature get accepted? ==
 +
Acceptance by the development team 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 development team that a particular feature is:
 +
# consistent with the goals and policies of Sugar
 +
# supported by the Sugar leadership
 +
# 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
    
== What do I need to do over the course of the release cycle? ==
 
== What do I need to do over the course of the release cycle? ==
3,267

edits