8,288
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + + + + + +
no edit summary
* When you try or test something, you learn what it has to offer.
* When you try or test something, you learn what it has to offer.
If in the course of your Sugar experiences, you discover something you want to share, you can report on your experiences here under one of the [[/Reports]] categories (or create a new one).
If in the course of your Sugar adventures, you discover something you want to share, you can report on your experiences here under one of the [[/Reports]] categories (or create a new one).
If you find software bugs, you can help the Sugar developers and others if you register a bug in our [http://bugs.sugarlabs.org bug tracker].
If you find software bugs, you can help the Sugar developers and others if you register a bug in our [http://bugs.sugarlabs.org bug tracker].
You will get a wider readership if you also report to the [http://lists.sugarlabs.org/listinfo/sugar-devel Sugar-devel mailing list].
* Testing requests - [[{{Previous Stable Release}}/Testing]], [[{{Current Stable Release}}/Testing]], [[{{Upcoming Stable Release}}/Testing]]
* Testing requests - [[{{Previous Stable Release}}/Testing]], [[{{Current Stable Release}}/Testing]], [[{{Upcoming Stable Release}}/Testing]]
== Page naming convention ==
When you create a report as a sub page of Testing/Reports/, think of including (but not limited to) some of the following in your page title. Sugar variant | host OS | version | machine. Use the subject of you report at the start of the page title, with other information qualifying the subject. To make your report part of an existing set by title, take, as a start, the beginning of an existing page title, and qualify it with your update.
== Testing Groups ==
== Testing Groups ==