Closed Bug 1170179 Opened 6 years ago Closed 6 years ago

Do not automatically set 'firefox-affected' release-tracking flags for comm-central products.

Categories

(bugzilla.mozilla.org :: General, defect)

Production
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: philip.chee, Assigned: glob)

References

Details

Attachments

(1 file)

comm-central products affected: SeaMonkey, Thunderbird, Mail News Core.
Just to be on the safe side add: Calendar (Lightning), Instantbird, Chat Core
following is a list of the products that field is currently visible on.

i suspect we should only automatically set affected on bugs filed against "firefox", "firefox for android", "firefox os", "core", and "toolkit" products.
al - does that look right to you?

Add-on SDK
addons.mozilla.org
Android Background Services
AUS
Core
Firefox
Firefox for Android
Firefox Health Report
Firefox OS
Loop
MailNews Core
Mozilla Localizations
Mozilla QA
Mozilla Services
NSPR
NSS
Other Applications
Plugins
Release Engineering
SeaMonkey
Snippets
Socorro
support.mozilla.org
Tech Evangelism
Testing
Toolkit
Webtools
www.mozilla.org
No longer blocks: 972040
Depends on: 972040
Flags: needinfo?(abillings)
I think you're missing some that would want the flag to remain:
Add-on SDK?
Firefox Health Report
Loop
Mozilla Services
Snippets?
Tech Evangelism?
Testing

I would recommend looking at which products have set that flag to "fixed" and use that as an indication of whether it's useful in that product. I would also err on the side of caution and only remove it from products that clearly don't want it as I can see website products (e.g. SUMO) theoretically using it as a way to track documentation changes related to a Firefox version.
(In reply to Byron Jones ‹:glob› from comment #1)
> following is a list of the products that field is currently visible on.
> 
> i suspect we should only automatically set affected on bugs filed against
> "firefox", "firefox for android", "firefox os", "core", and "toolkit"
> products.
> al - does that look right to you?

Yes, that looks right.
Flags: needinfo?(abillings)
(In reply to Matthew N. [:MattN] from comment #2)
> I think you're missing some that would want the flag to remain:

i'm not proposing removing that flag from those products, this is just about automatically setting it to "affected" when someone files a bug in that product using firefox/trunk.
OK, well I think at least Loop::Client should still have it set since it ships with Firefox and similar arguments can apply to Firefox Health Report (likely only the Client:* components) and some components of Mozilla Services.
(In reply to Matthew N. [:MattN] from comment #5)
> OK, well I think at least Loop::Client should still have it set since it
> ships with Firefox and similar arguments can apply to Firefox Health Report
> (likely only the Client:* components) and some components of Mozilla
> Services.

ok, i'll add Loop::Client and FHR::Client* to the list in comment 1.
should anyone else want this behaviour back they can file bugs.
Assignee: nobody → glob
Attached patch 1170179_1.patchSplinter Review
pans out loop doesn't have any versions configured, so it isn't impacted by this.
Attachment #8614730 - Flags: review?(dylan)
Comment on attachment 8614730 [details] [diff] [review]
1170179_1.patch

Review of attachment 8614730 [details] [diff] [review]:
-----------------------------------------------------------------

r=dylan

The tracking flags code is certainly an interesting place....
Attachment #8614730 - Flags: review?(dylan) → review+
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   ee8fcda..ee871d6  master -> master
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Depends on: 1263198
See Also: → 1269395
You need to log in before you can comment on or make changes to this bug.