Wednesday, 9 July 2014

Re: Bug reporting

On Wed, Jul 09, 2014 at 03:48:11AM -0800, Dave Higton wrote:
> On Wed, 09 Jul 2014 11:51:10 +0100 Richard Porter wrote:
>
> > On 8 Jul 2014 Dave Higton wrote:
> >
> >> The first thing the bug tracker asks is Category, which is a
> >> list of platforms from which I have to choose one, indicating
> >> that the bug is specific to a platform.
> >
> >> But, since I only have one platform, how do I know if what I'm
> >> reporting is specific to that platform?
> >
> > You don't but the developers may need to know what platform you are
> > running on. I take it to mean hardware platform since the OS and
> > version are asked for separately.
>
> OK, but that's not what it actually says. The options under
> "Category" are:
>
> ABEND
> Amiga-specific
> Atari-specific
> BeOS-specific
> Cocoa-sepcific
> Framebuffer-specific
> GTK-specific
> Javascript
> Layout
> RISC OS-specific
> Win32-specific
> [All Projects] General


If you are in any doubt of the category to use then use the General
category (it is a universal default category for all projects). For
you as a risc os user your options are limited to:

Javascript - issues obviously related to javascript.

Layout - Issues where the layout of the page is incorrect.

RISC OS-specific - Issues related to the RISC OS UI specifically, like
errors in the toolbar or configuration windows etc.

[All Projects] General - As already mentioned this is the default, if
you are unsure at all, just use this.

>
> I, as a user of a single OS, cannot tell whether the problem is
> specific to that OS, yet the field is required input from me.
>

The catagory is intended for issues specific to those OS frontends, if
you are not using them it cannot possibly be relevant to you. As I
outlined above, you (currently) have a choice of four.

> I don't want to make a big deal out of it, but it does look to
> be a misnomer, and I was just looking for some clarification of
> its significance to the developers. I've got it.
>
> AAMOI: what is the ABEND option about?

ABnormal END is a special classification for reported issues where the
program terminated abnormally with invalid state, literally the program
termination was abnormal. Generally these are aborts not caused by
assert() debug macros or our code dereferencing bad pointers those
are "normal" aborts.

This class is only useful to developers triaging bugs and I would hide
it from normal users if mantis allowed it.

>
> Dave
>
> ____________________________________________________________
> Protect your computer files with professional cloud backup.
> Get PCRx Backup and upload unlimited files automatically.
> Learn more at http://backup.pcrx.com/mail
>
>

--
Regards Vincent
http://www.kyllikki.org/

No comments:

Post a Comment