Changes

Jump to navigation Jump to search
m
this page is already archived
Line 1: Line 1: −
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
  −
   
=== Sugar Digest ===
 
=== Sugar Digest ===
   Line 10: Line 8:  
2. Leaning: There were some interesting discussions about learning on
 
2. Leaning: There were some interesting discussions about learning on
 
the Education list this week:
 
the Education list this week:
* [http://lists.lo-res.org/pipermail/its.an.education.project/2008-July/001275.html Sugar Labs, LOGO and Brian Harvey]
+
* [http://lists.sugarlabs.org/pipermail/iaep/2008-July/001275.html Sugar Labs, LOGO and Brian Harvey]
* [http://lists.lo-res.org/pipermail/its.an.education.project/2008-July/001279.html reconstructed maths]
+
* [http://lists.sugarlabs.org/pipermail/iaep/2008-July/001279.html reconstructed maths]
    
3. OLPC in the field: Jim Gettys has published an aggregate summary of
 
3. OLPC in the field: Jim Gettys has published an aggregate summary of
Line 47: Line 45:  
6. Release process: Marco Pesenti Gritti and Michael Stone have been
 
6. Release process: Marco Pesenti Gritti and Michael Stone have been
 
discussing how to integrate the Sugar and OLPC release processes:
 
discussing how to integrate the Sugar and OLPC release processes:
* SugarLabs should try to schedule its release a few months before the
+
* Sugar Labs should try to schedule its release a few months before the
 
OLPC release target date (something around 2–3 months). That will give
 
OLPC release target date (something around 2–3 months). That will give
 
us enough time to ensure everything is stable before we start
 
us enough time to ensure everything is stable before we start
Line 53: Line 51:  
* Sugar developers employed by OLPC will work on OLPC release
 
* Sugar developers employed by OLPC will work on OLPC release
 
contracts for all the new features present in the new release.
 
contracts for all the new features present in the new release.
* After the first stable release SugarLabs will keep releasing minor
+
* After the first stable release Sugar Labs will keep releasing minor
 
updates, which will include bug fixes and strings for the OLPC
 
updates, which will include bug fixes and strings for the OLPC
 
release.
 
release.
 
* We should make an effort to develop all the features required as
 
* We should make an effort to develop all the features required as
 
part of the unstable development cycle. Though there surely will be
 
part of the unstable development cycle. Though there surely will be
cases where OLPC will need changes outside the normal SugarLabs
+
cases where OLPC will need changes outside the normal Sugar Labs
 
schedule. We will land these in a limited and controlled way both
 
schedule. We will land these in a limited and controlled way both
 
during the freeze periods and as part of the stable minor releases.
 
during the freeze periods and as part of the stable minor releases.
Line 64: Line 62:  
7. Sucrose: Simon Schampijer announced the Sucrose Development Release
 
7. Sucrose: Simon Schampijer announced the Sucrose Development Release
 
0.81.6 this week
 
0.81.6 this week
([[Development Team/Release/Releases/Sucrose/0.81.6]]). You
+
([[0.82/0.81.6 Notes]]). You
 
can test it in OLPC joyride >= 2129.
 
can test it in OLPC joyride >= 2129.
   Line 76: Line 74:  
likely have problems updating to the latest version. Find instructions
 
likely have problems updating to the latest version. Find instructions
 
here to work around that problem
 
here to work around that problem
([[Development Team/Release/Releases/Sucrose/0.81.4#Instructions to test in olpc joyride]]).
+
([[0.82/0.81.4 Notes#Instructions to test in olpc joyride]]).
    
The sources can be found here:
 
The sources can be found here:

Navigation menu