Dextrose/3/Feature Freeze
Jump to navigation
Jump to search
TODO
- Triage these and these
- There are some unmerged patches on the @dx mailing list that tch sent some time ago. Those will close a few issues from above.
Blocker decisions needing debate
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 olpc.au and sl.o bug-trackers should be used for that.
Development goals
 |
This page has been marked as important but in need of updating as of May 2016. See all dated pages There may be relevant discussion on the talk page. |
To find the most up-to-date information on this content, please check https://sugardextrose.org/projects/dextrose/wiki/Dextrose_3_goals |
High priority
- Stability (looking towards current and future releases)
- 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 1
- Send to not reliable
- Data lost if collaboration is terminated and re-established
- Aggressive power management hindering XO collaboration
- OLPC tickets
- 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
- Configure essential network settings completely within sugar
- Share settings between Sugar and GNOME 1
- Share files between Sugar and GNOME 1
Low priority
Milestone blockers
Alpha-2
All items here which have a due date of 19th September should be closed.
Alpha-3
All items listed as Alpha-2 blockers closed.
All items here closed
All items here be discussed and closed.