Changes

:[3] http://wiki.sugarlabs.org/go/0.96/Notes

:[3] http://wiki.sugarlabs.org/go/0.96/Notes

:[4] http://en.wikipedia.org/wiki/Santalum_acuminatum

:[4] http://en.wikipedia.org/wiki/Santalum_acuminatum

==='''Customize your own remix of Sugar on a Stick.'''===

==='''Customize your own remix of Sugar on a Stick.'''===

 

Pineapple has a slightly larger Activity selection than its predecessor and has continued the trend of providing a few, better-tested Activities. We've realized that 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. See:

We realize that we'll never be able to create an Activity selection suitable for all deployments. Quandong now includes a set of teacher-tested Activities in the default image. The following links point the way to building alternative customizations.

#[[Build Your Own Remix with Fedora]]

#[[Build Your Own Remix with Fedora]]

#[http://download.sugarlabs.org/soas/docs/customization-guide customization guide]

#[http://download.sugarlabs.org/soas/docs/customization-guide customization guide]

#[http://wiki.sugarlabs.org/go/Sck/ASLOxo ASLO Activity Collection] DVD full of ASLO xo activities to Drag Drop into Soas Journal from DVD for Individual customizations.

#[http://wiki.sugarlabs.org/go/Sck/ASLOxo ASLO Activity Collection] DVD full of ASLO xo activities to Drag Drop into Soas Journal from DVD for Individual customizations.

'''Sugar on a Stick is a Fedora Spin.''' Since SoaS v3 Mirabelle, Sugar on a Stick has been recognized by the [http://fedoraproject.org Fedora Project] as an official [http://spins.fedoraproject.org Spin]. For the first time, SoaS Pineapple is going to be shipped on the Fedora Multi Spin DVD. This means we'll be shipping on the front a

'''Sugar on a Stick is a Fedora Spin.''' Sugar on a Stick is recognized by the [http://fedoraproject.org Fedora Project] as an official [http://spins.fedoraproject.org Spin]. These close ties with Fedora's release cycle and resources from their engineering and marketing teams extends the reach of Sugar on a Stick and makes the project itself more sustainable. In exchange, users of Fedora have access to an easily deployable implementation of the Sugar Platform; it's a great example of a mutually beneficial upstream–downstream relationship.

number of computer magazines across Europe and likely elsewhere in the coming months. These close ties with Fedora's release cycle and resources from their engineering and marketing teams extends the reach of Sugar on a Stick and makes the project itself more sustainable. In exchange, users of Fedora have access to an easily deployable implementation of the Sugar Platform; it's a great example of a mutually beneficial upstream–downstream relationship.

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

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

With v6 of Sugar on a Stick, the team recognizes the need to continue to improve its release processes and engineering sustainability. New contributors are urged to get involved and help us move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment.

The team recognizes the need to continue to improve its release processes and engineering sustainability. New contributors are urged to get involved and help us move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment.

If you'd like to contribute to the next version, [[Sugar on a Stick/v7|SoaS v7]], due for release in May of 2012, join our [http://lists.sugarlabs.org/listinfo/soas mailing list] and visit '''[[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 November of 2012, please join our [http://lists.sugarlabs.org/listinfo/soas mailing list] and visit '''[[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.

Thank you to all the people involved for their awesome work!

Thank you to all the people involved for their awesome work!

== Release history ==

== Release history ==

* SoaS v5 is based on Fedora 15, and was delayed. From the Fedora wiki,

and further information on previous releases may be found here: [[Sugar on a Stick/Project sitemap#Older versions of SoaS]]

*: "The move to NetworkManager 0.9 came after the feature freeze, and the Sugar desktop wasn't accounted for in the scramble to get alternate desktop environments working with it." [http://fedoraproject.org/wiki/Fedora_15_Retrospective#Could_have_been_better]

=== Re-approved as a Fedora Spin ===

<!-- === Feature process ===

The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is before the alpha release). They have to meet certain criteria by certain deadlines - if they don't, they're dropped and not eligible for mention as features. Major features must be in and testable by Alpha; minor changes need to be in and testable by Beta, after Beta only bugfixes are allowed.

 

 

 

 

<!-- The way features happen in Fedora is that early in the release process, developers propose features, and they are approved by a feature freeze date (which is before the alpha release). They have to meet certain criteria by certain deadlines - if they don't, they're dropped and not eligible for mention as features. Major features must be in and testable by Alpha; minor changes need to be in and testable by Beta, after Beta only bugfixes are allowed.

This feature process is not unique to Fedora. Feature processes are things that happen in basically every major FOSS project, and really in every major engineering project (even non-software) - it's how we systematically make sure we build something that's good and working.

This feature process is not unique to Fedora. Feature processes are things that happen in basically every major FOSS project, and really in every major engineering project (even non-software) - it's how we systematically make sure we build something that's good and working.

Since SoaS relies on both Sugar and Fedora as upstreams, we rely on their feature processes - most SoaS features come from either Fedora features or Sugar features. (For reference, our main upstreams are Fedora, Sugar Labs (sugar-core), ASLO (Activities), GNOME, and Python.) For v5, we built the release using a lightweight feature process for SoaS that inherits from those two upstreams. -->

Since SoaS relies on both Sugar and Fedora as upstreams, we rely on their feature processes - most SoaS features come from either Fedora features or Sugar features. (For reference, our main upstreams are Fedora, Sugar Labs (sugar-core), ASLO (Activities), GNOME, and Python.) For v5, we built the release using a lightweight feature process for SoaS that inherits from those two upstreams. -->

=== QA ===

== QA ==

:Much thanks to Peter Robinson who did a majority of the work to program, prepare and coordinate the work with many other sugar developers for this release.

Much thanks to Peter Robinson who did a majority of the work to program, prepare and coordinate the work with many other sugar developers for this release.

:Thomas Gilliard did field-testing (building real SoaS sticks from .iso files and testing on those) - it's the closest thing to systematic testing we've had yet, though we still have a ways to go.

:Thomas Gilliard did field-testing (building real SoaS sticks from .iso files and testing on those) - it's the closest thing to systematic testing we've had yet, though we still have a ways to go.

:Thank you also to James Cameron in Australia for his testing help!

:Thank you also to James Cameron in Australia for his testing help!

:Much help was also provided by the team at #fedora-qa; freenode IRC

:Much help was also provided by the team at #fedora-qa; freenode IRC

=== Documentation ===

== Documentation ==

<!-- We now have a [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide] and [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] as official documentation on how to custom-build an image and burn a SoaS stick, respectively. -->

<!-- We now have a [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide] and [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] as official documentation on how to custom-build an image and burn a SoaS stick, respectively. -->

A new release of documentation should come out with each new release of SoaS (although resources have prevented this).

A new release of documentation should come out with each new release of SoaS (although resources have prevented this).

The Fedora-site documentation may not be an improvement over our Sugar Labs, ad hoc wiki documentation methods, as the tools needed to participate are more complicated, and the Spin page documentation is not open to editing.  The Fedora Sugar on a Stick pages have not been edited since Mirabelle was released in May 2010. The attempt to better support a small number of known, working, "how to set up SoaS", instructions has not yet been fulfilled.

<!-- The Fedora-site documentation may not be an improvement over our Sugar Labs, ad hoc wiki documentation methods, as the tools needed to participate are more complicated, and the Spin page documentation is not open to editing.  The Fedora Sugar on a Stick pages have not been edited since Mirabelle was released in May 2010. -->

 

 

* Expanded discussion with upstream Fedora especially Fedora QA team and the new AutoQA processes. Initial integration in the Fedora Desktop QA testing process with initial guidelines and test process created. This will be expanded in Fedora 15 for the SoaS v5 release.

The attempt to better support a small number of known, working, "how to set up SoaS", instructions has not yet been fulfilled.

== Press coverage ==

== Press coverage ==

Feel free to add links to press coverage you find about Coconut to this section.

Feel free to add links to press coverage you find about Quandong to this section.