We have a chance to be uniform...I'm on board, let me understand how to report bugs.

Robert Pavich
Robert Pavich Member Posts: 5,685 ✭✭✭
edited November 21 in English Forum

I noticed that Pete was reporting bugs with the prefix "PH-B06" etc...

I don't know the significance of the PH but I'm guessing that B06 is "Bug number 6" so they can be tracked more effectively.

is this the format we are all going to follow?

Just want to blend in with the crowd here...

 

EDITED TO ADD: Ah...PH = Pete Holtzmann......got it.

So...are we going by this convention from now on?

Robert Pavich

For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__

Tagged:

Comments

  • Pete Holzmann
    Pete Holzmann Member Posts: 115

    I just did "something" that made sense to me (as a not-so-retired professional software destroyer :) )

    Here's the template I'm using. HAPPY to change or go with anything else. I just needed to organize my own thoughts!

    TITLE

      (Bug/Crash/Suggestion): III-xNN Description

    • Use a word at the start to categorize
    • "III" is the reporters initials, party to ensure all bug ID's are unique
    • "x" is currently B/C/S for the category
    • "NN" is the N'th item in that category... ideally unique across all beta testers but we can't guarantee that since multiple people might be writing reports as I type this :)
    • "Description" is brief summary

    CONTENT

    • Severity: currently Crash, Normal, Usability or Suggestion... oh or First Time Only
    • Symptoms: explain what you saw, and what was wrong with it
    • Workaround: have you found a way to get past this issue?
    • Be sure to also put your own setup in a footnote

    TAGS

    • Beta 1  (for this beta)
    • Bugs, Crashes, Suggestions

    I think that covers everything I have done so far. Ideas? Improvements? Brickbats? :)

  • Dave Dunkin (Logos)
    Dave Dunkin (Logos) Member, Logos Employee Posts: 1,043

    It's not necessary for you to assign identifiers to bug reports; we won't use them. We have our own internal bug tracking system.

    The best bug reports are the ones that have a clear title, a description of what happened, what you expected to happen instead and what steps one can take to reproduce it. Information about your device, model and version of Android, are also helpful.

    Thanks,

    Dave.

  • Robert Pavich
    Robert Pavich Member Posts: 5,685 ✭✭✭
    https://community.logos.com/discussion/comment/258227#Comment_258227

    Ok Dave...I'm on board with that...that's much easier, and it's the way I'm used to from the other forum.

    Robert Pavich

    For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__

  • Pete Holzmann
    Pete Holzmann Member Posts: 115
    https://community.logos.com/discussion/comment/258227#Comment_258227

    No prob. Just eliminates the "code" part of the format :)

Categories