Re: Bugzilla summary



Martin Baulig <martin home-of-linux org> writes:

> Hi,
> 
> trying to make this a bit more productive, do you guys (all you who
> commented so in detail about operating system names) really thing
> this needs to be so much detailed here ?
> 
> I think we can pretty well go with a more general list like
> 
>         Platforms:
> 
>                 Unspecified
>                 All
>                 Alpha
>                 Risc
>                 PowerPC
>                 Intel x86
>                 MIPS
>                 Sparc
> 
>         OS:
> 
>                 Unspecified
>                 All
>                 AIX
>                 BSD
>                 HP-UX
>                 IRIX
>                 Linux
>                 Digital Unix
>                 SunOS/Solaris
> 
> where "Sparc" stands for any Sparc and "SunOS/Solaris" stands for any
> "SunOS/Solaris".
> 
> People can include in their bug reports what exact platform and operating
> system they have.
> 
> I think we really need to restrict these list to major, general platforms
> and operating systems since otherwise we'd end up adding and adding and
> adding stuff to this list while Bugzilla is already running.

Is it possible to implement my suggestion of a general OS selector
plus a text entry where the bug reporter just fills in whatever else
they think is relevant?  (e.g. Red Hat Linux for Sparc 7.0beta)

I simply think that trying to keep track of all versions all
distributors and architectures is a losing battle...

What do other people think of that idea? It hurts searching a bit
but you should still be able to do text searches, and I don't
think searching on platform/architecture is all that common
or interesting.
 
> > >         WORKSFORME
> > >                 All attempts at reproducing this bug were futile, reading
> > >                 the code produces no clues as to why this behavior would
> > >                 occur. If more information appears later, please re-assign
> > >                 the bug, for now, file it.
> > >                 (some people suggested adding a new INCOMPLETE, but I think
> > >                  we can use WORKSFORME for this).
> 
> Just got some feedback from a frequent bug reporter in personal mail and he
> suggested to rename this to INCOMPLETE since this gives people a better idea
> about what is wrong (the developer needs more info).

But WORKSFORME is so fun to select... ;-)

                                        Owen

[ There are cases were either WORKSFORME or INCOMPLETE would be
  more accurate - it probably doesn't matter which we take ]




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]