Dextrose/Getting Involved

NOTE: The content of this page is considered DEPRECATED and OBSOLETE It is preserved for historical research, along with its talk page. Moved and died at https://sugardextrose.org/projects/dextrose/wiki/Testing_and_reporting_issues Dextrose   ·   Get Involved   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings Development If you want to create custom images, see the documentation of the Dextrose build system. Testing Feedback from the entire community is appreciated. Reporting bugs upstream If you know the specific upstream project that contains the bug, please file your report into their bug tracker: Sugar and activities: http://bugs.sugarlabs.org/ Drivers and OLPC customizations: http://dev.laptop.org/ Fedora OS: http://bugzilla.redhat.com/ When you file a bug on any component which affects Dextrose, please bring it to our attention by marking it with the "dextrose" keyword and by Cc'ing the Dextrose Release Manager. Reporting bugs specific to Dextrose You can file bugs specific to Dextrose in the Sugar Labs bug tracker and assign them to component "Dextrose". You can use this component when you're in doubt, the maintainers will reassign it to the correct component. Before you file a new bug, please check the Summary of all bugs affecting Dextrose to avoid duplicates. You can comment on existing bugs to provide additional details. Test plans We currently don't have a formal test plan for Dextrose. We're looking for someone to help us coordinate our QA effort. These are some useful starting points: SoaS V4 Activity Test Table (2010) 0.88 test plan from Paraguay Educa (incomplete, 2010) OLPC 8.2.0 (aka os801): Test Cases, Test Results (obsolete, 2008) OLPC testing matrix (obsolete, 2007)