Please do not edit unless you are part of the Sugar Release Team!
Sucrose 0.92 Release Notes
- 1 Introduction
- 2 What is new for users
- 3 What is new for distributors and deployers
- 4 What's new for developers
- 5 What's new for packagers
- 6 Internationalization (i18n) and Localization (l10n)
- 7 Compatibility
- 8 Update to this version
- 9 Getting the sources
- 10 Installing/running 0.92
- 11 Looking at the release cycle details
- 12 Credits
Sucrose 0.92 is the latest version of the Sugar learning platform: Sugar promotes collaborative learning through Sugar Activities that encourage critical thinking, the heart of a quality education. Designed from the ground up especially for children, Sugar offers an alternative to traditional “office-desktop” software. Furthermore it provides a flexible and powerful platform for activity developers.
Sugar is Free and Open Source Software and consists of Glucose, the base system environment; and Fructose, a set of demonstration activities. This new release contains many new features, performance and code improvements, bug fixes, and translations.
What is new for users
What is new for distributors and deployers
What's new for developers
The following changes are important for developers using the Sucrose 0.90 developer platform.
Activity Authors guidelines
There are still many activities that do not use the new activity toolbars introduced in 0.86. We encourage activity authors to use the new toolbars as there have been huge improvements in usability (e.g., stopping an activity).
Jim Simmons has written a guide to writing Sugar Activities (Please see Make your own Sugar Activities!) which details how to convert your activity to the new toolbars while still keeping backward compatibility with older Sugar versions.
What's new for packagers
Internationalization (i18n) and Localization (l10n)
Update to this version
Please use the instructions for your distribution (SoaS, Fedora, Ubuntu, Debian, etc.) of choice to upgrade to this release. Note that it may take a while until the release is packaged for each distribution. Please stay tuned for distribution specific announcements and watch out for updates at Get Sugar.
Getting the sources
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the Sugar git repositories.
- sugar 0.92.1
- sugar-datastore 0.92.1
- sugar-toolkit 0.92.1
- sugar-base 0.92.0
- sugar-presence-service 0.90.2
- sugar-artwork 0.92.0
- etoys 4.1.2390
- hulahop 0.7.1
- Pippy 40
- Browse 122
- Calculate 35
- Etoys 116
- Chat 70
- TurtleArt 108
- Jukebox 20
- Log 24
- ImageViewer 17
- Write 73
On Fedora from the shell:
yum groupinstall sugar-desktop
will install Sugar 0.92 as a GDM selection on login.
yum install sugar-emulator
to run Sugar in a full screen window in a Gnome session. See how to make a desktop icon to do this.
Note: You may need to disable SELinux (See http://www.crypt.gen.nz/selinux/disable_selinux.html)
Looking at the release cycle details
You can browse the notes of each development release in 0.92/Roadmap#Schedule. Their respective sources are listed there as well.
Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.
We want to especially thank:
- the Infrastructure team which does all this great work in the background without which the development would not be possible at all,
- the deployments that provide the development team with feedback from the field,
- the Design team which guided the design of features with UI changes or impact on the workflow,
- the Translation team which makes sure that Sugar is enjoyable in the local languages of our users,
- the developers that submit patches for new features and bug fixes and do review other's patches,
- the maintainers that make sure their code is shippable and which provide packagers with new tarballs,
- the packagers which provide distributions with new Sugar packages,
- the SoaS team for providing a Sugar version to test with during the development cycle,
- the testers for finding the small and bigger issues,
- the release team and Development team for coordinating those efforts.