Sucrose 0.112 Release Notes

Introduction

Sugar 0.112 is a new stable release of the Sugar Learning Platform. It was released on TODO: Date

What is new?

  • Updated translations,
  • New Save-As feature which can be enabled in GSettings by deployments who wish to enforce journal entry naming,
  • Shut down automatically before battery is fully dead,
  • Remove an activity from the frame entirely when it is stopped, even if it does not stop properly,
  • Make sure the journal entry chooser appears in front of the running activity, without needing alt+tab,
  • Make sure the radio off button works every time it is used,
  • Better support for external displays on a laptop or desktop computer.

What is new for developers?

  • Updated README for installing for developing with Sugar and Sugar Toolkit,
  • New busy cursor methods for activities, see busy(),
  • New Gtk.Entry option for Alert, see add_entry(),
  • Accept ~ as a version separator in activities, see bundleversion,
  • Better background for image box in View Source,
  • Updated documentation for Sugar Toolkit API, see sugar3,
  • Predictable POT file ordering,
  • Several warnings removed from logs.

Tarballs

How to contribute with testing?

Please visit our testing section to see all the alternatives to test this new release.

Credits

Patches contributors

  • Besnik Bleta,
  • Chris Leonard,
  • Eduard Sanou,
  • Ezequiel Pereira,
  • Gonzalo Odiard,
  • György Balló,
  • Hrishi Patel,
  • Ignacio Rodríguez,
  • Manash Raja,
  • Sam Parkinson,
  • Sanchit Kapoor,
  • Utkarsh Tiwari,

Special thanks to our Google Code-In and Google Summer of Code students for their contributions over the past year.

Translations contributors

TODO?

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, Toast and Debian 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, _TODO_ took the responsibility of managing the release.