When someone uploads an extension, they might not know that there is a GUID for Mozilla 1.x that would let Moz be autodetected. We could add a "Helpful Hint" if they manually set the extension as being Mozilla 1.x compatible. "Helpful Hint: Update.mozilla.org will read Mozilla 1.x compatibility from your RDF if it is present. This will have no impact on Mozilla 1.x itself."

Code bugs should not be filed against the QA, particularly if you ever want them to even be found. heh. We shouldn't even be assigning anything to that address. All bugs should be owned by somebody. (even if it's nobody.) and extension/theme updates shouldn't *ever* touch nobody.

I don't understand the difference. "Nobody" means "Nobody's working on this, feel free to take it"

That works for code bugs.. but doesn't work for extension/theme bugs, as most people don't have access, so therefore it should always be assigned to somebody with access. and the default QA's list is pretty much a blackhole where nobody will ever see it, which is bad, things can get lost there.

Bulk Moving Developer Control Panel bugs to new component. (Filter: massdevcpspam)

This will apply to any minver that's set manually.

Comment on attachment 169115 [details] [diff] [review] Prompt the user during manual minver selection This will cause that tip to be a nag, every time they change MinAppVer, as it's a JS alert on onchan ge. That tip also gives basicallly no information that they would need to include the section. This isn't worth having a nagging prompt like that. review-

Yes, I designed it specifically to be a nag. What text would you like to see included in it? What is your suggestion for a different location for alterting the user? By placing it as a nag, it was much easier to code than trying to detect otherwise whether Mozilla 1.x was ever selected.

Replacing with bug 290683