Re: Sucrose 0.83.1 Development Release
At noon Nov 4 I'm viewing the amount of 0.83 available in Joyride (it's approximately zero) as indicative of the consideration being shown by the Sugarlabs and the OLPC communities to those who are not running jhbuild. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sucrose 0.83.1 Development Release
On Tue, Nov 4, 2008 at 9:15 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote: At noon Nov 4 I'm viewing the amount of 0.83 available in Joyride (it's approximately zero) as indicative of the consideration being shown by the Sugarlabs and the OLPC communities to those who are not running jhbuild. Mikus, we are working on it. Unfortunately it's not trivial and we don't want to push something completely unusable to joyride. Be patient, you should be aware that we are only three developers working full time on Sugar and we have way too many things to deal with... Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Sucrose 0.83.1 Development Release
Tomeu Vizoso wrote: On Fri, Oct 31, 2008 at 9:30 PM, S Page [EMAIL PROTECTED] wrote: Simon Schampijer wrote: This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. Will OLPC joyride builds pick up the new Sucrose? Sure. Hopefully soon. Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. What happens when you upgrade an XO with the old datastore? The old datastore will be updated to the new format. What happens if you then downgrade it? You lose. Sugar moved to use Gconf as a back end to store the profile. When you upgrade an XO, does it import your old profile (~olpc/.sugar/default/config)? Yup. What happens if you then downgrade? You will be prompted to enter again a name, choose a color, etc. Right when we upgrade the old profile is ported to gconf and the .sugar/default/config file is erased - so when we downgrade we check for the presence of that file and will create the config like we do on first boot. An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Where are they marked, in the .py files? Yes, in the docstrings so it should make it to places like http://api.sugarlabs.org == Fructose news == ... Are the new activity versions backwards-compatible with 8.2? If so, the maze of Activity lists should be updated. Most of them yes, a notable exception is Browse because depends on xulrunner and hulahop. Read has the same issue, but evince hasn't been updated (yet) so for now it should work. Currently http://wiki.laptop.org/go/Activities/Joyride pulls in Activities/G1G1 , as does Activities/G1G1/8.2, and that list still references old versions -- Browse 98 not 100, Read 52 not 60, etc. -- even though the links say Browse (latest). Who could take care of this? Activities/G1G1/8.2 is right to pull in Browse 98 - since the latest browse is dependent on the latest hulahop. The others should be updated I guess. Best, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Sucrose 0.83.1 Development Release
On Fri, Oct 31, 2008 at 9:30 PM, S Page [EMAIL PROTECTED] wrote: Simon Schampijer wrote: This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. Will OLPC joyride builds pick up the new Sucrose? Sure. Hopefully soon. Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. What happens when you upgrade an XO with the old datastore? The old datastore will be updated to the new format. What happens if you then downgrade it? You lose. Sugar moved to use Gconf as a back end to store the profile. When you upgrade an XO, does it import your old profile (~olpc/.sugar/default/config)? Yup. What happens if you then downgrade? You will be prompted to enter again a name, choose a color, etc. An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Where are they marked, in the .py files? Yes, in the docstrings so it should make it to places like http://api.sugarlabs.org == Fructose news == ... Are the new activity versions backwards-compatible with 8.2? If so, the maze of Activity lists should be updated. Most of them yes, a notable exception is Browse because depends on xulrunner and hulahop. Read has the same issue, but evince hasn't been updated (yet) so for now it should work. Currently http://wiki.laptop.org/go/Activities/Joyride pulls in Activities/G1G1 , as does Activities/G1G1/8.2, and that list still references old versions -- Browse 98 not 100, Read 52 not 60, etc. -- even though the links say Browse (latest). Who could take care of this? Full Release Notes: http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.83.1 Maybe you could address these questions in a ==Compatibility== section in the release notes. Yes, I agree this is an important issue that should be given greater relevance in the release notes. The changes and fixes sound excellent! More coming! Thanks, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Sucrose 0.83.1 Development Release
This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. To improve performance several heavy shell dependency have been dropped and the journal and the shell service has been merged into the shell. Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. Sugar moved to use Gconf as a back end to store the profile. An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Some enhancements have been made to the clipboard to provide visual consistency with the Sugar environment. And of course many many bugs have been fixed, which you can see in detail below. Thanks to everyone who made this release possible! In behalf of the sugar community, Your release team Full Release Notes: http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.83.1 Sucrose Release Schedule: http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Schedule == Glucose news == === sugar-toolkit === * Mark modules as STABLE/UNSTABLE/DEPRECATED * #8420 Failure to handle 404 in ChunkedGlibHTTPRequestHandler * #7649 Activities needs to access sugar-toolbox's members directly * #8617 Clipboard scroll buttons icons point left/right, should point up/down * #8604 Tray control should support highlight on drag * #8840 Can't join shared activity * #8674 8.2-764, Software Update erased complete /home/olpc/Activities directory * #8626 Icons overlap unnecessarily in crowded neighborhood view. * #8563 Sugar Palette doesn't handle 'table menus'. * #8532 SIGCHLD fights with threads. * #8485 Shell navigation leaks * #8375 gst usage in the shell wastes 2.6mb * #8394 sugar shell leaks presence service info * #8469 palette.menu is leaked * #8394 sugar shell leaks presence service info * #8392 Remove dynamic font height computation * #5428 downloads not starting in Browse due to old compreg.dat * #7999 7+% of shell startup time is spent in `grab' of sugar._sugarext.KeyGrabber * #8000 Pulsing icon on activity launch significantly slows activity start-up * #7270 setup release does not update the bundle number * #7959 gettext translations slows journal's scrolling * #7733 Cannot install Wikipedia-10.xo * #7533 Activity does not respond to ctrl-q keyboard shortcut unless the 'Activity' tab is visible === sugar === * Modularized the shell to have every major UI component like the frame the home view and the control panel reside in his own module and be self contained * Use gconf as a backend to store the profile. * Several heavy shell dependency have been dropped. * Merge of the journal and of the shell service into the shell * #5867 Battery fully charged shows up in error (battery is removed) * #8623 Jabber server description is ambiguous * #8900 Should re-request closed random views * #7545 Should request random activities/buddies to populate the mesh view * #5751 Clipboard objects need meaningful labels. * #8606 Dragging within the clipboard creates duplicate clippings * #7408 Cursor lock while dragging icons in Home (or anywhere) * #8604 Tray control should support highlight on drag === sugar-artwork === * Ensure that all common drag operations use a sugar cursor * Generate two themes based on SUGAR_SCALING * #8779 Merge sugar-artwork patches from debian package. * #8778 allow prelightning of buttons === sugar-base === * Add dispatcher implementation from django * Mark modules as STABLE === sugar-datastore === * The datastore has been rewritten, to simplify and improve maintainability. As a first step the API was not changed at all (other than removing removable devices support), so that the new implementation was swapped in without changes to activities and Sugar * Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS * #8155 The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND * Support arbitrary metadata properties that activities wish to add #4662 * Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem #6269 === sugar-presence-service === * #7581: Don't ignore buddies without keys. This improve interoperability with non Sugar clients. * #7849: Display PS version in the log. * Use gconf to get Sugar profile settings. * #8444: Don't rely on the roster to check if a contact handle is channel specific or not - so PS will properly create Buddy objects discovered using Gadget. Furthermore, this workaround has the nice side effect to improve compatibility with bugged shared roster (as the one of ejabberd). * #5618: Discard invalid handles if InspectHandles failed. === etoys === This
Re: Sucrose 0.83.1 Development Release
Simon Schampijer wrote: This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. Will OLPC joyride builds pick up the new Sucrose? Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. What happens when you upgrade an XO with the old datastore? What happens if you then downgrade it? Sugar moved to use Gconf as a back end to store the profile. When you upgrade an XO, does it import your old profile (~olpc/.sugar/default/config)? What happens if you then downgrade? An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Where are they marked, in the .py files? == Fructose news == ... Are the new activity versions backwards-compatible with 8.2? If so, the maze of Activity lists should be updated. Currently http://wiki.laptop.org/go/Activities/Joyride pulls in Activities/G1G1 , as does Activities/G1G1/8.2, and that list still references old versions -- Browse 98 not 100, Read 52 not 60, etc. -- even though the links say Browse (latest). Full Release Notes: http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.83.1 Maybe you could address these questions in a ==Compatibility== section in the release notes. The changes and fixes sound excellent! -- =S ugar Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
