I have used other bug trackers that have something like an "AVAILABLE" state to indicate that a bug is actionable or confirmed, but that no one is currently working on it. Such a state is very useful. Would such a thing be useful here, and would it make sense to try and use NEW for that (although I find NEW to be a bad choice of names for this), or is that just not practical?
-- Dirk On Mon, Jun 20, 2011 at 10:04 AM, Alexey Proskuryakov <[email protected]> wrote: > > 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 WebKit bug database. While I can imagine projects where >> those are used to communicate something helpful to bug management, this is >> not true of our project at this time. > > > I previously objected to removing UNCONFIRMED, since NEW practically meant > "someone who knows what an actionable bug looks like has seen this", and I've > been using this distinction when choosing whether to open a bug from my RSS > feed. This distinction has eroded since then, so I also think that we don't > need UNCONFIRMED any more. > > - WBR, Alexey Proskuryakov > > _______________________________________________ > 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
