Features/Policy: Difference between revisions

Line 57:

== Propose a feature for addition into the release cycle ==

The final goal is to have a feature present in a stable release. Once the ownership is sorted out and the page is filled out correctly you can propose it to the release manager for inclusion into the process. The proposer of the feature and the owner can be the same person.

The final goal is to have a feature present in a stable release. There are three major steps needed:

In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.

# Owner: The Feature must have a clear owner (The proposer of the feature and the owner can be the same person).

# Community consensus: You must reach consensus about the Feature in the community.

# Summary of the feature

## Send an email to sugar-devel mailing list with ''[FEATURE]'' tag in the subject asking for feedback. This is to give the community, in particular the deployments, the chance to comment.

# A designated owner with a link to Sugar home page. The owner is responsible for:

## If your feature adds UI or changes the current UI please add as well the ''[DESIGN]'' tag to the subject. The Design Team should be involved in the discussion to guarantee a consistent design and a consistent work flow in Sugar.

## making sure the feature is completed according to the schedule

# Documentation: In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.

## communicating periodic status

#* Summary of the feature

## attending feature status meetings

#* A designated owner with a link to Sugar home page. The owner is responsible for:

# Current status

#** making sure the feature is completed according to the schedule

## last updated

#** communicating periodic status

## estimated percentage of completion

#** attending feature status meetings

# Description of the new feature

#* Current status

# Detailed explanation of what the new feature will do and how it will be implemented

#** last updated

# Benefit to Sugar

#** estimated percentage of completion

# Scope

#* Description of the new feature

# How To Test

#* Detailed explanation of what the new feature will do and how it will be implemented

# Dependencies--on other packages or features

#* Benefit to Sugar

# Contingency plan

#* Scope

# Link to documentation

#* How To Test

# Important information for release notes

#* Dependencies--on other packages or features

# 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.

#* Contingency plan

#* Link to documentation

#* Important information for release notes

#* 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.

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.

@@ Line 57: / Line 57: @@
 == Propose a feature for addition into the release cycle ==
-The final goal is to have a feature present in a stable release. Once the ownership is sorted out and the page is filled out correctly you can propose it to the release manager for inclusion into the process. The proposer of the feature and the owner can be the same person.
+The final goal is to have a feature present in a stable release. There are three major steps needed:
-In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.
+# Owner: The Feature must have a clear owner (The proposer of the feature and the owner can be the same person).
+# Community consensus: You must reach consensus about the Feature in the community.
-# Summary of the feature
+## Send an email to sugar-devel mailing list with ''[FEATURE]'' tag in the subject asking for feedback. This is to give the community, in particular the deployments, the chance to comment.
-# A designated owner with a link to Sugar home page. The owner is responsible for:
+## If your feature adds UI or changes the current UI please add as well the ''[DESIGN]'' tag to the subject. The Design Team should be involved in the discussion to guarantee a consistent design and a consistent work flow in Sugar.
-## making sure the feature is completed according to the schedule
+# Documentation: In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.
-## communicating periodic status
+#* Summary of the feature
-## attending feature status meetings
+#* A designated owner with a link to Sugar home page. The owner is responsible for:
-# Current status
+#** making sure the feature is completed according to the schedule
-## last updated
+#** communicating periodic status
-## estimated percentage of completion
+#** attending feature status meetings
-# Description of the new feature
+#* Current status
-# Detailed explanation of what the new feature will do and how it will be implemented
+#** last updated
-# Benefit to Sugar
+#** estimated percentage of completion
-# Scope
+#* Description of the new feature
-# How To Test
+#* Detailed explanation of what the new feature will do and how it will be implemented
-# Dependencies--on other packages or features
+#* Benefit to Sugar
-# Contingency plan
+#* Scope
-# Link to documentation
+#* How To Test
-# Important information for release notes
+#* Dependencies--on other packages or features
-# 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.
+#* Contingency plan
+#* Link to documentation
+#* Important information for release notes
+#* 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.
 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.