On Tue, Jun 21, 2011 at 5:33 AM, Darin Adler <[email protected]> wrote: > On Jun 20, 2011, at 12:30 PM, Ryosuke Niwa wrote: > >> For all practical purposes, NEW has been equivalent to AVAILABLE in WebKit. > > To me it seems that WebKit’s closer equivalent of AVAILABLE is Assigned To = > [email protected]
It looks like new bugs from anonymous users are automatically created both UNCONFIRMED and Assigned To = [email protected]. This would preclude using Assigned To = [email protected] as an indicator of AVAILABLE in Dirk's sense, right? FWIW we (the Chrome team in Sydney) have been triaging CSS UNCONFIRMED bugs and putting actionable ones into the NEW state for the last quarter or so. We tend to weed out about half of the reported bugs, so this feels useful :) Cheers, -Shane > -- Darin > > PS: Apologies to everyone for hijacking this thread. I now realize I should > have started a new one to respond to the comment about UNCONFIRMED. > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
