Features/Policy: Difference between revisions

Line 82:

# Put a ''watch'' on your page so you are notified when its category changes. You must be logged in, then click the ''watch'' link at the top of the page.

=== ~~How does~~ a feature ~~get accepted?~~ ===

Once the feature owner believes that the feature is ready for presentation to the Release Manager for ''acceptance'' move your feature from [[:Category:Feature Page Incomplete]] to [[:Category:Feature Ready for Release Manager]]. The Release Manager will then do the sanity check.

=== Acceptance of a feature ===

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.

Line 91:

Line 93:

# 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? ===

If the Feature is accepted the Release Manager moves the Feature to Feature Accepted <version>, such as, [[:Category:Feature Accepted {{Upcoming Stable Release}}]]. If the feature is denied the Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission.

=== What do the feature owner need to do over the course of the release cycle? ===

# Feature pages should be updated to reflect the current status of the feature by the following milestones on the [[Development_Team/Release/Roadmap | Release schedule]]:

#* Alpha Freeze --features not 100% complete at alpha should be updated no less than every two weeks

@@ Line 82: / Line 82: @@
 # Put a ''watch'' on your page so you are notified when its category changes.  You must be logged in, then click the ''watch'' link at the top of the page.
-=== How does a feature get accepted? ===
+Once the feature owner believes that the feature is ready for presentation to the Release Manager for ''acceptance'' move your feature from [[:Category:Feature Page Incomplete]] to [[:Category:Feature Ready for Release Manager]]. The Release Manager will then do the sanity check.
+=== Acceptance of a feature ===
 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.
@@ Line 91: / Line 93: @@
 # 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? ===
+If the Feature is accepted the Release Manager moves the Feature to Feature Accepted <version>, such as, [[:Category:Feature Accepted {{Upcoming Stable Release}}]]. If the feature is denied the Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission.
+=== What do the feature owner need to do over the course of the release cycle? ===
 # Feature pages should be updated to reflect the current status of the feature by the following milestones on the [[Development_Team/Release/Roadmap | Release schedule]]:
 #* Alpha Freeze --features not 100% complete at alpha should be updated no less than every two weeks