We should at least move your suggested removals to the bottom of the new bug page, given their lower bug filing volume. For instance, SeaMonkey had ~75 bugs filed in the last month while Firefox for Android (lower on the list) had closer to 500.
-Alex On Mar 18, 2013, at 2:14 PM, Jason Smith <jsm...@mozilla.com> wrote: > Sounds good to me. > > Also to add in a piece of private feedback I received - SeaMonkey wants to > remain on the front page as there's a strong community behind it that still > works on that project. > > Sincerely, > Jason Smith > > Desktop QA Engineer > Mozilla Corporation > https://quality.mozilla.com > > On 3/18/2013 9:39 AM, L. David Baron wrote: >> On Monday 2013-03-18 09:27 -0700, Jason Smith wrote: >>> *existing canconfirm access* *enter bug entry page list* >>> >>> - Core >>> - Firefox >>> - Thunderbird >>> - Calendar >>> - Camino >>> - SeaMonkey >>> - Firefox for Android >>> - Mozilla Localizations >>> - Mozilla Labs >>> - Mozilla Services >>> - Other Products >>> >>> *existing no canconfirm access enter bug entry page list* >>> >>> - Firefox >>> - Firefox for Android >>> - Thunderbird >>> - Mozilla Services >>> - SeaMonkey >>> - Mozilla Localizations >>> - Mozilla Labs >>> - Calendar >>> - Core >> I'd actually like to see Core higher on the list for the >> no-canconfirm case. I think it's common for reasonably >> well-informed Web developers (who would have been able to choose a >> reasonably correct component within Core, given the list) to file >> standards bugs and end up with them languishing in Firefox::General. >> And I think appropriate guiding for Web developers filing bugs >> against the rendering engine is an important case. >> >> -David >> > > _______________________________________________ > 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
