Re: status-firefox41: affected
On 01/06/2015 12:18, glob wrote: > this started happening via > https://bugzilla.mozilla.org/show_bug.cgi?id=972040 > > please file a bug and we'll apply per-product filtering -- currently > it'll be set on any product that has that flag. I have filed https://bugzilla.mozilla.org/show_bug.cgi?id=1170179 > (i'm not sure why seamonkey has that flag visible on its bugs) And Thunderbird, Mail News Core. Phil -- Philip Chee , http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: status-firefox41: affected
this started happening via https://bugzilla.mozilla.org/show_bug.cgi?id=972040 please file a bug and we'll apply per-product filtering -- currently it'll be set on any product that has that flag. (i'm not sure why seamonkey has that flag visible on its bugs) -glob Philip Chee wrote: On 31/05/2015 16:02, Sylvestre Ledru wrote: I don't know about this specific issue but I asked to Ryan a few months back that the status firefox would be automatically marked as "fixed" for the current nightly. I guess this is related to this. Yahbutt the flag doesn't get changed to fixed when I close said SeaMonkey bug. The "affected" status flags being automatically set started a few weeks ago. It's hard to imagine how a bug about (say) the toilets in Mountain View backing up could affect firefox Phil ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: status-firefox41: affected
On 31/05/2015 16:02, Sylvestre Ledru wrote: > I don't know about this specific issue but I asked to Ryan a few > months back that the status firefox would be automatically marked as > "fixed" for the current nightly. I guess this is related to this. Yahbutt the flag doesn't get changed to fixed when I close said SeaMonkey bug. > The "affected" status flags being automatically set started a few > weeks ago. It's hard to imagine how a bug about (say) the toilets in Mountain View backing up could affect firefox Phil -- Philip Chee , http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: status-firefox41: affected
I don't know about this specific issue but I asked to Ryan a few months back that the status firefox would be automatically marked as "fixed" for the current nightly. I guess this is related to this. The "affected" status flags being automatically set started a few weeks ago. Sylvestre Le 31/05/2015 05:29, Jared Wein a écrit : > Bugzilla has defaulted to marking new bugs as status-firefoxXX: affected. > I'm not sure when it started but this is why. > > Hope that helps, > Jared > > On Sat, May 30, 2015 at 11:58 AM, Philip Chee wrote: > >> Why are these SeaMonkey bugs flagged status-firefox41: affected >> >> https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey >> >> Why are these SeaMonkey bugs flagged status-firefox40: affected >> >> https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox40&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey >> >> Thunderbird: >> >> https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&list_id=12290869&o1=equals&v1=affected&f1=cf_status_firefox40&o3=equals&v3=affected&query_format=advanced&f3=cf_status_firefox40&f2=OP&product=MailNews >> Core&product=Thunderbird >> >> History doesn't show anyone manually marking these bugs >> status-firefox40/status-firefox41 >> >> Some filter rule going bonkers? >> >> Phil >> >> -- >> Philip Chee , >> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org >> Guard us from the she-wolf and the wolf, and guard us from the thief, >> oh Night, and so be good for us to pass. >> ___ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: status-firefox41: affected
Bugzilla has defaulted to marking new bugs as status-firefoxXX: affected. I'm not sure when it started but this is why. Hope that helps, Jared On Sat, May 30, 2015 at 11:58 AM, Philip Chee wrote: > Why are these SeaMonkey bugs flagged status-firefox41: affected > > https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey > > Why are these SeaMonkey bugs flagged status-firefox40: affected > > https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox40&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey > > Thunderbird: > > https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&list_id=12290869&o1=equals&v1=affected&f1=cf_status_firefox40&o3=equals&v3=affected&query_format=advanced&f3=cf_status_firefox40&f2=OP&product=MailNews > Core&product=Thunderbird > > History doesn't show anyone manually marking these bugs > status-firefox40/status-firefox41 > > Some filter rule going bonkers? > > Phil > > -- > Philip Chee , > http://flashblock.mozdev.org/ http://xsidebar.mozdev.org > Guard us from the she-wolf and the wolf, and guard us from the thief, > oh Night, and so be good for us to pass. > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
