it has to be somebody's task to read *every* unconfirmed misc issues i have done that for the issues posted since i got the privileges (in June) up to September and tagged/CCed what i could... but now that my semester is starting I no longer have enough time to do that (it's a whole day of work just trying to keep up with the issues flow)
the thought of the many issues i now lag behind (and will probably never get to) is disturbing. it seems to me that currently new misc issues are triaged almost randomly too bad i can no longer contribute as much as i want On Oct 16, 12:35 am, "Mark Larson (Google)" <[email protected]> wrote: > Area-Misc bugs had a bit of a hiccup in triage, but we're looking at them > regularly again. > This bug was Unconfirmed, not Untriaged. We don't do a good job of looking > at those bugs. It's an issue on my list, but not something I have anyone > actively working on. > > > > On Mon, Oct 12, 2009 at 11:53, Jeremy Orlow <[email protected]> wrote: > > I think the bigger issue is how/when Area-Misc bugs get triaged. Do they > > ever? If not, we should probably change that. > > > On Mon, Oct 12, 2009 at 11:50 AM, Guria <[email protected]> wrote: > > >> Please confirm the bug > >>http://code.google.com/p/chromium/issues/detail?id=12900 > >> It really annoys me. > >> I expect that someone will fix it soon. I can provide more examples if > >> needed. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
