We should probably turn off the UNCONFIRMED state. At this time in the WebKit
project there is no useful distinction between UNCONFIRMED and NEW.
I haven’t seen any useful distinction between UNCONFIRMED, NEW, ASSIGNED, and
REOPENED in the WebKit bug database. While I can imagine projects where
20.06.2011, в 9:42, Darin Adler написал(а):
We should probably turn off the UNCONFIRMED state. At this time in the WebKit
project there is no useful distinction between UNCONFIRMED and NEW.
I haven’t seen any useful distinction between UNCONFIRMED, NEW, ASSIGNED, and
REOPENED in the
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 =
webkit-unassig...@lists.webkit.org
-- Darin
PS: Apologies to everyone for hijacking
On Tue, Jun 21, 2011 at 5:33 AM, Darin Adler da...@apple.com 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 =
4 matches
Mail list logo