Difference between revisions of "Dextrose/Getting Involved"

From Sugar Labs
Jump to navigation Jump to search
Line 3: Line 3:
 
== Testing ==
 
== Testing ==
  
Besides community testing and field testing, we're planning to reuse and extend the
+
Feedback from the entire community is appreciated. Please use the appropriate bug
OLPC test plan adopted in release 8.2.0 (aka os801): http://wiki.laptop.org/go/TestPlan_8.2.0
+
tracker for each upstream component:
  
Feedback from the entire community is appreciated. Bugs belonging to upstream
 
components should be filed in the usual trackers:
 
 
* Bugs specific to the Dextrose build: http://bugs.sugarlabs.org/wiki/Dextrose
 
 
* Sugar and activities: http://bugs.sugarlabs.org/
 
* Sugar and activities: http://bugs.sugarlabs.org/
* Fedora 11: http://bugzilla.redhat.com/
 
 
* Drivers and OLPC customizations: http://dev.laptop.org/
 
* Drivers and OLPC customizations: http://dev.laptop.org/
 +
* Fedora OS: http://bugzilla.redhat.com/
 +
* Bugs specific to Dextrose: http://bugs.sugarlabs.org/ (assign to component "Dextrose")
  
If you file a bug which affects Dextrose in the Sugar and OLPC trackers,
+
* Summary of bugs affecting Dextrose: http://bugs.sugarlabs.org/wiki/Dextrose
 +
 
 +
If you file a bug which affects Dextrose in the Sugar or OLPC trackers,
 
please mark it with the "dextrose" keyword to bring it to our attention.
 
please mark it with the "dextrose" keyword to bring it to our attention.
 
  
 
== Test plans ==
 
== Test plans ==

Revision as of 14:04, 14 August 2010

Dextrose   ·   Get Involved   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

Testing

Feedback from the entire community is appreciated. Please use the appropriate bug tracker for each upstream component:

If you file a bug which affects Dextrose in the Sugar or OLPC trackers, please mark it with the "dextrose" keyword to bring it to our attention.

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: