0.104/Notes

Sucrose 0.104.0 Release Notes

Introduction

Sugar 0.104 is the new STABLE version of the Sugar learning platform. It was released on February the 13th 2015. This release includes new features and bug fixes from Google Code-In and Summer of Code students, deployments and community members.

Summary of new features

• Extended microformat updater with optional activities in automatic updates [1].
• New dconf setting to disable adhoc autoconnect policy [2].
• New "spent-times" entry in activities metadata [3].
• New "New ASLO" back-end for activities updates [4].
• New text-to-speech API in gtk3 toolkit [5].
• Customizable groups instead of fixed ages in "About Me" section.

This is the full list of features proposed, we expect to re-evaluate unmerged proposals in the next release cycle.

Tarballs

• sugar
• sugar-toolkit-gtk3
• sugar-artwork
• sugar-datastore
• sugar-runner

How to contribute with testing

We will provide more options for testing this release soon. For now, please try it out using sugar-build.

Credits

Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education distributions, packaging, and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.

Patches contributors

• Sam Parkinson
• Ignacio Rodríguez
• Ezequiel Pereira Lopez
• Daksh Shah
• Goutam
• James Cameron
• Walter Bender
• Gonzalo Odiard
• Martin Abente Lahaye

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.

This time, Martin Abente Lahaye took the responsibility of manage the release.