Changes

no edit summary
Line 11: Line 11:  
== Testing ==
 
== Testing ==
   −
Feedback from the entire community is appreciated. Please use the appropriate bug
+
Feedback from the entire community is appreciated.
tracker for each upstream component:
+
 
 +
=== 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/
 
* Sugar and activities: http://bugs.sugarlabs.org/
Line 18: Line 21:  
* Fedora OS: http://bugzilla.redhat.com/
 
* 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/Contacts|Dextrose Release Manager]].
   −
== Reporting bugs ==
+
=== Reporting bugs specific to Dextrose ===
* Bugs specific to Dextrose: http://bugs.sugarlabs.org/ (assign to component "Dextrose")
  −
* Summary of bugs affecting Dextrose: http://bugs.sugarlabs.org/wiki/Dextrose
     −
When you file a bug on any component which affects Dextrose, please bring it to our
+
You can file bugs specific to Dextrose in the [http://bugs.sugarlabs.org/ Sugar Labs bug tracker] and
attention by marking it with the "dextrose" keyword and by Cc'ing the Release Manager.
+
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 [http://bugs.sugarlabs.org/wiki/Dextrose Summary of all bugs affecting Dextrose]
 +
to avoid duplicates. You can comment on existing bugs to provide additional details.
   −
== Test plans ==
+
=== Test plans ===
    
We currently don't have a formal test plan for Dextrose. We're looking for someone to
 
We currently don't have a formal test plan for Dextrose. We're looking for someone to