User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20101203 (CK-xxxxxxxxxx) Firefox/3.6.13 (.NET CLR 3.5.30729) Build Identifier: While 'mid-air collision' may be considered witty or cute, it has some very negative connotations in certain environments. Coming from an Air Traffic Control world, I've had to change this error far too many times. A more professional, and more descriptive, error would be Save Conflict. Reproducible: Always
WONTFIX? Why not? Someone can't spend 10 minutes to review a simple, 7-line patch?
Similar to "zarro boogs found", the phrase "mid-air collision" is a cornerstone Bugzilla phrase that has been used for years. As such, we have no interest in changing it. Even our documentation notes this potential problem: http://www.bugzilla.org/docs/3.6/en/html/cust-templates.html#template-specific "bug/process/midair.html.tmpl: This is the page used if two people submit simultaneous changes to the same bug. The second person to submit their changes will get this page to tell them what the first person did, and ask if they wish to overwrite those changes or go back and revisit the bug. The default title and header on this page read "Mid-air collision detected!" If you work in the aviation industry, or other environment where this might be found offensive (yes, we have true stories of this happening) you'll want to change this to something more appropriate for your environment."
I think that "zarro boogs" serves a purpose to remind the user to double check their spelling. Including a warning "This may be offensive" doesn't sound like something that should be included in this caliber of a program, even if it has been around for 10+ years. (prior to 2.16 as far as I can see in a 2 minute search) I equate it to having a severity of 'Completely Fooked' as a default setting.
Hey Mike. I understand your point, but it's only offensive in the airline industry. Otherwise it is a standard term that we have been using for over 10 years and refer to all over the place. I don't see a strong need to change this in the core product.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.