Bug Tracker - rules of engagement
This is a discussion on Bug Tracker - rules of engagement within the cvpcs forums, part of the Droid Forums Dev Archives category; We have been getting a ton of erroneous bugs listed in the bug tracker of late. So I am going to lay down a few ...
-
Bug Tracker - rules of engagement
We have been getting a ton of erroneous bugs listed in the bug tracker of late. So I am going to lay down a few ground rules. If these rules are not followed we will throw your bug out without even looking into it as we have nothing to go on to help track down the issue.
1.) SEARCH - Before posting a bug search, check to see if someone has already posted a bug of the same or similar problem. If it is similar, but not the "exact" same add a comment to the existing similar bug. If it is a totally different bug we will make a listing for it.
2.) LOGCAT - when a true bug occurs, we need a logcat of the offending error so that we have an idea of where to look for the offending issue. Without this just telling us that your phone crashed doesn't get us anywhere near a solution to the issue. If you do not know how to produce a logcat there is an app as well as guides online to teach you how.
3.) REPRODUCIBILITY - each bug that is logged needs to have the steps documented for reproducing the offending error so that it will help us pin down what is causing the error. Sometimes the error is actually in a different program than what is being loaded, and said program isn't playing nice with previously loaded software.
4.) APPS -
a.) XXX app is not showing up in the market, we can't help that. it is up to the app maker to make it available in froyo. This is also NOT a bug at all, it is due app developers lack of updating the app to be compatible with the latest release.
b.) XXX app is force closing on your rom. It doesn't happen on XXX rom. See #2 & #3. If it is actually a bug we will gladly look into the cause if the app is the cause there isn't much we can do about it.
5.) THEMES - verify whether any bugs are theme related or rom related. To do so reload the stock rom only and verify the bug still exists. If not the bug needs to be posted under the themes section.
Logcat info: http://bit.ly/aiid8i
If you are able to follow this criteria please post your bug reports at: Bugzilla Main Page
Last edited by sniffle; 08-16-2010 at 07:21 PM.
"i want to punch motorola in the face, then i want to shove my droid x down his throat and when he starts choking say "oh sorry, apparently your throat isn't signed properly for loading air into your lungs" - cvpcs
-
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
Similar Threads
-
By right in forum Droid Applications
Replies: 11
Last Post: 05-30-2010, 02:25 PM
-
By withersdavid in forum New Member Introductions & Site Assistance
Replies: 1
Last Post: 05-03-2010, 01:52 PM
-
By droidavie in forum Motorola Droid
Replies: 2
Last Post: 03-05-2010, 03:38 PM
-
By sho_greg in forum Droid Applications
Replies: 1
Last Post: 12-10-2009, 04:28 PM
Search tags for this page
can verizon tell if your phone tapped or bugged
,
how can i tell if my droid is bugged?
,
how can i tell if my droid phone is tapped
,
how can i tell if my droid x is bugged
,
how can i tell if my verizon droid is bugged?
,
how can i tell if my verizon droid x is bugged
,
how do you tell if your droid x is tapped
,
how to find out if phone is bugged
,
how to find out if your android has been bugged
,
how to knoow if you are bugged or tapped droid phone
,
how to tell if your iphone is bugged
,
is my droid bugged
Click on a term to search our site for related topics.