Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion bugzilla.mozilla.org improvements
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Benjamin Smedberg  
View profile  
 More options Jun 12 2009, 12:26 pm
Newsgroups: mozilla.dev.planning
From: Benjamin Smedberg <benja...@smedbergs.us>
Date: Fri, 12 Jun 2009 09:26:52 -0700
Local: Fri, Jun 12 2009 12:26 pm
Subject: Re: bugzilla.mozilla.org improvements
Print | View thread | Show original | Report this message | Find messages by this author
On 6/12/09 4:35 AM, Gervase Markham wrote:

> Please say what the change you are requesting is, and why making it
> would improve your life. References to previous discussions and bug
> numbers would help.

* Remove the Hardware and OS fields:

The Hardware/OS fields are constantly misunderstood or misused: bug-filers
don't know whether they mean "I'm using windows" or "this bug is
windows-specific", and this means that the data is inconsistent, which makes
searching based on the OS/Hardware meaningless. Asking bug filers to fill in
metadata that isn't actually required is an unnecessary burden.

* Remove the severity field

The "blocker" and "enhancement" severities actually mean something to us
currently, but everything inbetween is basically "a bug of some sort"
without much actionable difference. I think we should instead have a
"blocking trunk" flag which we use to mark bugs which should close the
mozilla-central tree, and an enhancement keyword to mark enhancement bugs.

* Combine Status and Resolution

Status and Resolution always come in pairs... it seems silly to have two
fields where one would do quite well.

* Track FIXEDness per-branch

This is by far the hardest and most pie-in-the-sky request, but one which I
think would be most valuable.

--BDS


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google