Changes

</noinclude>

</noinclude>

{|

[[File:SugaronastickMirabelle.png|450px|right|a Sugar environment you can carry in your pocket!|link=http://archive.kernel.org/fedora-alt/spins/linux/releases/13/Spins/]]

|-

 

| style="border: 0; border-width: 0;" |

{{admon/note|Notice|Sugar on a Stick v3 '''Mirabelle''' has been superseded by the [[Sugar on a Stick/Mango Lassi|Mango Lassi]] release as of 02 November 2010. See http://spins.fedoraproject.org/soas for the most current version.}}

 

== Sugar on a Stick - Mirabelle ==

== Sugar on a Stick - Mirabelle ==

: ''a Sugar environment you can carry in your pocket''

: ''a Sugar environment you can carry in your pocket''

Mirabelle is the most recent release of the '''[[Sugar on a Stick]]''' project. It was released on '''25 May 2010.''' Mirabelle is named after the [[wikipedia:Mirabelle | Mirabelle plum]].

Mirabelle is the most recent release of the '''[[Sugar on a Stick]]''' project. It was released on '''25 May 2010.''' Mirabelle is named after the [[wikipedia:Mirabelle | Mirabelle plum]].

== Release announcement ==

== Release announcement ==

We are proud to announce the availability of [[Sugar on a Stick]] v.3, code-named Mirabelle. More information about Sugar on a Stick, including download and installation details, is available at http://spins.fedoraproject.org/soas/.

We are proud to announce the availability of [[Sugar on a Stick]] v3, code-named Mirabelle. More information about Sugar on a Stick, including download and installation details, is available at http://spins.fedoraproject.org/soas/.

<span class="linkgroup">[[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]</span>

<span class="linkgroup">[[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]</span>

|-

|-

| style="border: 0; border-width: 0;" |  

| style="border: 0; border-width: 0;" |  

'''Customize your own remix of Sugar on a Stick.''' You'll notice that v.3 Mirabelle has a smaller Activity selection than its predecessors, Blueberry and Strawberry. We realized we'll never be able to create an Activity selection suitable for all deployments - instead, we've chosen to include and support a core set of basic, teacher-tested Activities in the default image, and invite deployments to use this as a base on which to build a customized Activity selection for their classrooms. Instructions on how to do this are available at http://download.sugarlabs.org/soas/docs/customization-guide/. A quick, but less pristine, method of build customization is available at [[Sugar on a Stick/Sugar Clone]].

'''Customize your own remix of Sugar on a Stick.''' You'll notice that v3 Mirabelle has a smaller Activity selection than its predecessors, Blueberry and Strawberry. We realized we'll never be able to create an Activity selection suitable for all deployments - instead, we've chosen to include and support a core set of basic, teacher-tested Activities in the default image, and invite deployments to use this as a base on which to build a customized Activity selection for their classrooms. Instructions on how to do this are available at http://download.sugarlabs.org/soas/docs/customization-guide/. A quick, but less pristine, method of build customization is available at [[Sugar on a Stick/Sugar Clone]].

| style="border: 0; border-width: 0; width: 120px;" |[[File:Cici-stick.jpg|120px|right|http://download.sugarlabs.org/soas/docs/customization-guide/]]

| style="border: 0; border-width: 0; width: 120px;" |[[File:Cici-stick.jpg|120px|right|http://download.sugarlabs.org/soas/docs/customization-guide/]]

|}

|}

=== Contributing to Sugar on a Stick ===

=== Contributing to Sugar on a Stick ===

The biggest difference in v.3 of Sugar on a Stick has been in its release processes and engineering sustainability; it's now much easier for new contributors to get involved. We continue to move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment, and invite all interested parties to join us.

The biggest difference in v3 of Sugar on a Stick has been in its release processes and engineering sustainability; it's now much easier for new contributors to get involved. We continue to move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment, and invite all interested parties to join us.

If you'd like to contribute to the next version, due for release in early November, join us at our Contributors Portal at '''[[Sugar on a Stick]]'''. All types of contributions are welcome, from the technical to the pedagogical, and we're happy to teach what we know and learn what you have to share.

If you'd like to contribute to the next version, due for release in early November, join us at our Contributors Portal at '''[[Sugar on a Stick]]'''. All types of contributions are welcome, from the technical to the pedagogical, and we're happy to teach what we know and learn what you have to share.

=== Notes for the future ===

=== Notes for the future ===

* Pick SoaS v.4 color combos soon.

* Pick SoaS v4 color combos soon.

* Sync with Design earlier in the release cycle for color-choosing, etc.

* Sync with Design earlier in the release cycle for color-choosing, etc.

* There's a FUDCon in September in Zurich, we may want to look at that as a Sugar/SoaS meetup opportunity.

* There's a FUDCon in September in Zurich, we may want to look at that as a Sugar/SoaS meetup opportunity.

* Send fortnightly release schedule emails to the SoaS list about upcoming milestones

* Send fortnightly release schedule emails to the SoaS list about upcoming milestones

* Activity Inclusions Criteria to be finalized for v.4

* Activity Inclusions Criteria to be finalized for v4

* Track core libraries and dependencies more closely, especially for Activity developers - make sure our upstreams are also in sync with each other, and that it's clear whose responsibility it is to keep track of what.

* Track core libraries and dependencies more closely, especially for Activity developers - make sure our upstreams are also in sync with each other, and that it's clear whose responsibility it is to keep track of what.

* It would be good if we could enable a python option to close check the api and break the build if there's something missing / changed.

* It would be good if we could enable a python option to close check the api and break the build if there's something missing / changed.