+1 to suggestions from Lawrence and Milan. The info is still pretty
important for the QA team, and we definitely do NOT want it gone.
Regards,
Florin.
-Original Message-
From: dev-platform
[mailto:dev-platform-bounces+florin.mezei=softvisioninc...@lists.mozilla.org
] On Behalf Of Byron
bugzilla has a set of fields, hardware and operating system, that
i'll collectively call platform in this post. their default values
are detected from the reporter's user-agent string when a bug is created.
unfortunately on bmo, the platform fields have two distinctly different
meanings: the
Are the platform fields actually useful? Most bugs apply to all platforms
and in the cases that don't it is normally clear from the bug conversation
that it is platform specific. It seems like we rarely go an update the
platform fields to match the actual state of the bug. And then there is the
Having that field be wrong is worse than not having it, no doubt about that,
but if we had a way of making sure that field actually contains correct
information, it would be extremely useful to the graphics team.
I don’t have the numbers, but it certainly feels like a large majority of the
On Tue, Apr 14, 2015 at 8:40 AM, Dave Townsend dtowns...@mozilla.com
wrote:
Are the platform fields actually useful? Most bugs apply to all platforms
and in the cases that don't it is normally clear from the bug conversation
that it is platform specific. It seems like we rarely go an update
On 4/14/2015 11:40 AM, Dave Townsend wrote:
Are the platform fields actually useful? Most bugs apply to all platforms
and in the cases that don't it is normally clear from the bug conversation
that it is platform specific. It seems like we rarely go an update the
platform fields to match the
+1 to Milan's suggestion. These fields are used somewhat consistently on
stability and graphics bugs, which release management pays attention to. If
we are going to continue with the fields, I like the idea of Not
specified as that makes it clear that no value was set whereas All is
currently used
Lawrence Mandel wrote:
+1 to Milan's suggestion. These fields are used somewhat consistently
on stability and graphics bugs, which release management pays
attention to. If we are going to continue with the fields, I like the
idea of Not specified as that makes it clear that no value was set
On 4/14/15 8:40 AM, Dave Townsend wrote:
I've gotten used to just
ignoring these fields and reading the bugs instead. I wouldn't feel any
loss if they were just removed from display entirely.
+1. The fields are broadly unreliable, and we should just remove them. I
think I've seen the
+1
On Tue, Apr 14, 2015 at 3:59 PM, Justin Dolske dol...@mozilla.com wrote:
On 4/14/15 8:40 AM, Dave Townsend wrote:
I've gotten used to just
ignoring these fields and reading the bugs instead. I wouldn't feel any
loss if they were just removed from display entirely.
+1. The fields are
10 matches
Mail list logo
