5,705
edits
Changes
Jump to navigation
Jump to search
Line 121:
Line 121: − + − + − + − + − + − + − + − +
→0.3
* Consider running the system in Fedora-11 (current in use in Peru).
* Consider running the system in Fedora-11 (current in use in Peru).
* <strike>Distribute base software updates.</strike> Moved to 0.4.
* <strike>Distribute base software updates.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> Moved to 0.4.
* <strike>Start gathering [[Platform_Team/Usage_Statistics|usage statistics]].</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Define/Document some useful usage indicators for SN interaction.</strike> Moved to 0.4.
* <strike>Define/Document some useful usage indicators for SN interaction.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>More useful client behavior in offline scenario, e.g. show content accessible locally.</strike> Initial implementation in place.
* <strike>More useful client behavior in offline scenario, e.g. show content accessible locally.</strike> Initial implementation in place.
* <strike>Optimize current implementation to make it more useful on XO-1 laptops.</strike> The second shell start (after calling {{Code|sugar}} command and before appearing Journal icon) for 40 installed activities is only 6 seconds longer than with Dextrose-3.
* <strike>Optimize current implementation to make it more useful on XO-1 laptops.</strike> The second shell start (after calling {{Code|sugar}} command and before appearing Journal icon) for 40 installed activities is only 6 seconds longer than with Dextrose-3.
* <strike>Setup -testing server instance that will keep regular SN content that should be migrated to new code base on every release.</strike>. Sugar Shell looks for http://api-testing.network.sugarlabs.org by default, there is also read-only public web server, http://network-testing.sugarlabs.org.
* <strike>Setup -testing server instance that will keep regular SN content that should be migrated to new code base on every release.</strike>. Sugar Shell looks for http://api-testing.network.sugarlabs.org by default, there is also read-only public web server, http://network-testing.sugarlabs.org.
* <strike>Setup translation.sugarlabs.org translation process.</strike> Moved to 0.4.
* <strike>Setup translation.sugarlabs.org translation process.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Handle server notifications about SN data changes in client application.</strike> Moved to 0.4
* <strike>Handle server notifications about SN data changes in client application.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Synchronization between SN nodes.</strike> Moved to 0.4.
* <strike>Synchronization between SN nodes.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Basic i18n support in SN content (excluding managing already entered strings).</strike>
* <strike>Basic i18n support in SN content (excluding managing already entered strings).</strike>
* <strike>Basic routines for SN editors (including initial populating SN content):</strike> 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.
* <strike>Basic routines for SN editors (including initial populating SN content):</strike> 0.3 will contain only trivial and ready use activities, the editors workflow implementation work will start from 0.4.
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> Moved to 0.4.
* <strike>Since there are useful binary based activities (GC, TuxPaint), support upload such activities to SN. From developers point of view, the only they need to proceed is uploading sources bundle to SN, the rest (building sources for all supported platforms) should happen automatically.</strike> <span style="color: red">Moved to 0.4.</span>
* <strike>Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.</strike> Thanks to [[User:Satellit|satellit]], testing server contains only activities that start without problems.
* <strike>Revise most popular ASLO activities to add all needed meta information (like required dependencies) and mark the as stable and ready to run from Sugar Network.</strike> Thanks to [[User:Satellit|satellit]], testing server contains only activities that start without problems.
* <strike>Worfklow to semi automatic collect fail reports using Report resource.</strike> Move to 0.25.
* <strike>Worfklow to semi automatic collect fail reports using Report resource.</strike> Move to 0.25.
* <strike>final XO image, for students and teachers (teachers server), that is ready for deploying.</strike> Moved to 0.4.
* <strike>final XO image, for students and teachers (teachers server), that is ready for deploying.</strike> <span style="color: red">Moved to 0.4.</span>
=== 0.4 ===
=== 0.4 ===