166
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Dextrose/3/Feature Freeze (view source)
Revision as of 03:48, 20 August 2011
, 03:48, 20 August 2011no edit summary
This page is a stub for listing dextrose-3 related features and bugs identified on a priority basis. This page is '''NOT''' meant for regular tracking of their completion. The [http://dev.laptop.org.au olpc.au] and [http://bugs.sugarlabs.org sl.o] bug-trackers should be used for that
This page is a listing of dextrose-3 related features and bugs identified on a priority basis. This page is '''NOT''' meant for regular tracking of their completion. The [http://dev.laptop.org.au olpc.au] and [http://bugs.sugarlabs.org sl.o] bug-trackers should be used for that.
=Development goals=
==High priority==
* Stability (looking towards current and future releases)
** Yum based updater [http://dev.laptop.org.au/issues/800 1] [http://dev.laptop.org.au/issues/851 2]
** Offline updates method [http://dev.laptop.org.au/issues/873 1]
* No regressions w.r.t earlier dx-2 or olpc.au releases
** '''TODO''' Identify bug-id's here
* '''Solid collaboration experience''' : This seems to be the most high-priority set of tasks, which are blockers in real terms. Need to fix the most critical ones
** Regressions in collaboration [http://dev.laptop.org.au/issues/737 1]
** [http://dev.laptop.org.au/issues/788 Send to not reliable]
** [http://dev.laptop.org.au/issues/729 Data lost if collaboration is terminated and re-established]
** [http://dev.laptop.org.au/issues/636 Aggressive power management hindering XO collaboration]
** OLPC tickets
*** [http://dev.laptop.org/ticket/10674 10674]
*** [http://dev.laptop.org/ticket/10749 10749]
*** [http://dev.laptop.org/ticket/10750 10750]
*** [http://dev.laptop.org/ticket/10676 10676]
*** [http://dev.laptop.org/ticket/10677 10677]
*** [http://dev.laptop.org/ticket/10801 10801]
*** [http://dev.laptop.org/ticket/10821 10821]
*** [http://dev.laptop.org/ticket/11074 11074]
*** [http://dev.laptop.org/ticket/11073 11073]
*** [http://dev.laptop.org/ticket/11075 11075]
* QA, (& maybe validation?)
* Stable and efficient dextrose development environment
** Discussed this with silbe. Maybe have a custom jhbuild env privately, and a public one once 0.94 is released, otw. rebasing might be a problem. Another way out which was suggested was to have multiple branches with rebase of dx patches on top.
==Medium Priority==
* Share files with a server
* Better Sugar/Gnome integration
* Upstreaming
==Low priority==
* Collection of usage statistics
* VM image
=Alpha-2=
=Alpha-3=
=Beta-1=
=Beta-2=
=Release=