779
edits
Changes
Sugar on a Stick release process (view source)
Revision as of 14:16, 21 June 2010
, 14:16, 21 June 2010→Feature process
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What do I get with a feature?'' Having your feature approved not only helps everybody involved in the development and engineering process to keep track of its state, but also allows other teams - like the [[Marketing_Team|marketing team]] - to leverage your work and promote it.
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''What are my responsibilities?'' By signing up for a feature, you sign up for taking care of it. That means you'll be the one responsible for providing updates and interacting with the different teams concerned by your feature, like the release engineering for Sugar on a Stick. It does, however, not mean that you've to realize your feature all alone - go out and tell the [http://lists.sugarlabs.org lists] and the [http://planet.sugarlabs.org planet] about your work. Get people excited to help you!
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''
* ''How does evaluation happen?'' Your proposal needs a majority of ''YAY'' votes from the release team (determined for a given release by the release manager - the v4 release manager is Sebastian Dziallas, and the current relase team is formed by Peter Robinson, Mel Chua and Sebastian Dziallas) to get approval. Discussion will happen at a weekly meeting, while the decisions will be announced to the SoaS mailing list.'''
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.
* ''What if my feature got rejected?'' No worries! Features that are originally rejected can be revised and resubmitted.
=== How to submit a feature for consideration ===
# Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. ('''TODO:''' create ''Category:SoaS_v4_Feature'' so people can make their pages belong to the appropriate category so that we know which version you're targeting ).
# Place a link to your proposal in the [[#Current feature ideas]] section of this page while you're working on the document.
# Send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
# When you think your feature proposal is ready, move it to the [[#Features submitted for review]] section of this page. It will be brought up at the next [[Sugar on a Stick meeting]], where it'll be evaluated and voted on. We might ask you to make further adjustments and revisit it at a later point or approve the feature directly. We're looking forward to hearing about your ideas!
=== Approved features for the current release ===
=== Approved features for the current release ===