Changes

Jump to navigation Jump to search
6,229 bytes added ,  05:01, 17 September 2012
Created page with "<noinclude>{{ Translations | english }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Categ..."
<noinclude>{{ Translations | [[0.94/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team. Comments are welcome on the [[{{TALKPAGENAME}}|Discussion page]].''

<span style="font-size:188%">Sucrose 0.96 Release Notes</span>

== Introduction ==
Sugar 0.98 is the new version of the [http://www.sugarlabs.org/ Sugar learning platform]. It will be released the November the 07th 2012 (see [[0.98/Roadmap#Schedule]] for details).

The main changes in this cycle will be the ported Shell to use GTK+ 3 and Pygobject3 and the touch support in the UI.

== What is new for users ==

== What's new for developers ==

=== Activity Authors guidelines ===
The most important change is that the GTK+ 2 based sugar-toolkit has been deprecated since Sugar 0.96. Newly written activities should use sugar-toolkit-gtk3, which is based on GTK+ 3 and Pygobject3, now. There will be only bug fixes being available in the future for the old toolkit no new features will be made available for it and it will probably go away at one point completely. Detailed guidelines for porting existing activities can be found at [[Features/GTK3/Porting]].

=== Widgets ===

=== API ===
Please see the [[0.96/Notes#API]] for which API has been removed during the switch from toolkit-gtk2 to toolkit-gtk3.

=== Tutorials ===
There is a brand new [[Activity_Team/Activity_Development_Fedora 17|step-by-step guide]] for developing Activities under Fedora 17.

== What's new for packagers ==
* python-cjson is no longer a dependency of Sugar

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==
Activities that has been ported to sugar-toolkit-gtk3 will not run on older Sugar versions where the new toolkit is not available. Which means latest Browse and Read will not run on Sugar versions < 0.96. This is reflected in the activity providing backend ASLO where the activities are marked >= 0.96 only.

== 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 [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.96.2.tar.bz2 sugar 0.96.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.96.0.tar.bz2 sugar-datastore 0.96.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.96.3.tar.bz2 sugar-toolkit 0.96.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.96.3.tar.bz2 sugar-toolkit-gtk3 0.96.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.96.0.tar.bz2 sugar-base 0.96.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.96.3.tar.bz2 sugar-artwork 0.96.3]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-5.0.2403.tar.gz etoys 5.0.2403]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-46.tar.bz2 Pippy 46]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-138.tar.bz2 Browse 138]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-40.tar.bz2 Calculate 40]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-76.tar.bz2 Chat 76]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-139.tar.bz2 TurtleArt 139]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-23.tar.bz2 Jukebox 23]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-28.tar.bz2 Log 28]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-20.tar.bz2 ImageViewer 20]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-79.tar.bz2 Write 79]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-36.tar.bz2 Terminal 36]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-99.tar.bz2 Read 99]

== How to contribute with testing ==

==Credits==
This cycle we want to especially thank the contributors to the GTK+ 3/pygobject3 port of the shell! Thanks to Daniel Narvaez for all his help here.

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 | ''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 | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''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 [[Sugar_on_a_Stick | ''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 | ''Development team'']] for coordinating those efforts.

== Looking forward to [[1.0]]==
In the [[1.0]] we want to focus on the API and fix all the little Todos and Fixmes we never got around to.
3,267

edits

Navigation menu