Difference between revisions of "Sugar on a Stick release process"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* ''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! | ||
| − | * ''What do I have to do now?'' Fill out the [[Features/Feature_Template|template]] and stick it on a page in the wiki. | + | * ''What do I have to do now?'' |
| − | * | + | #* 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! | ||
* ''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. | ||
| + | |||
| + | === Approved features for the current release === | ||
| + | |||
| + | ''Features must be added to this list by a member of the release team. Place complete feature proposals in the [[#Features submitted for review]] section for consideration at the next meeting.'' | ||
=== Features submitted for review === | === Features submitted for review === | ||
Revision as of 14:15, 21 June 2010
Feature process
The feature process for Sugar on a Stick aims at providing a structured way of implementing and keeping track of upcoming features for the next release of Sugar on a Stick. This document outlines the guidelines for submitting feature proposals. An important thing to realize is the release schedule for each release.
- What is a feature? A feature is defined as a significant change or enhancement to the version of Sugar on a Stick currently under development that may or may not include new packages and also relate to features of both Fedora and Sugar
- What are the deadlines? The deadlines for the release currently under development are outlined in the release schedule.
- 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 - 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 lists and the planet about your work. Get people excited to help you!
- What do I have to do now?
- Fill out the 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 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!
- 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.
Approved features for the current release
Features must be added to this list by a member of the release team. Place complete feature proposals in the #Features submitted for review section for consideration at the next meeting.
Features submitted for review
These will be considered at the next Sugar on a Stick meeting. Only submit proposals you believe are complete.
- Sugar Creation Kit DVD [1]
- ASLOxo (Also included on SCK DVD: over 140 ASLO.xo files to put on a second USB stick for installing activities by drag-drop into the sugar Journal of a running Soas Stick.) [2]
Current feature ideas
These feature ideas are in various stages of development.
- School server
- Kickstart generator
- Sugar Creation Kit DVD [3]
- ASLOxo (Also included on SCK DVD: over 140 ASLO.xo files to put on a second USB stick for installing activities by drag-drop into the sugar Journal of a running Soas Stick.) [4]
- Revised Browse default bookmarks_html [5]
- btrfs and snapshots
- systemd
- More robust iso