779
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − '''This page is a stub.''' It hasn't yet been filled in, but will be filled in soon - in the meantime, see [[Sugar on a Stick]] for more details about the project as a whole, or email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] with any questions. If you can help start filling in this page, please jump in and edit! − Line 11:
Line 9: − +
Sugar on a Stick release process (view source)
Revision as of 21:38, 7 June 2010
, 21:38, 7 June 2010no edit summary
== Feature process ==
== Feature process ==
* ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. Most importantly, make it belong to the appropriate category so that we know which version you're targeting ('''TODO:''' create ''Category:SoaS_v4_Feature''). Finally, send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
* ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. Most importantly, make it belong to the appropriate category so that we know which version you're targeting ('''TODO:''' create ''Category:SoaS_v4_Feature''). Finally, send an email to the SoaS [http://lists.sugarlabs.org/listinfo/soas list] and incorporate any feedback you might receive.
* ''What will happen then?'' After you've incorporated feedback from the mailing lists and the proposal fits the guidelines listed above, we'll stick it on the agenda for the next of our [[Sugar_on_a_Stick_meetings|meetings]] 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!
* ''What will happen then?'' After you've incorporated feedback from the mailing lists and the proposal fits the guidelines listed above, we'll stick it on the agenda for the next of our [[Sugar_on_a_Stick_meetings|meetings]] 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!
* ''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 for that release and currently 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.