fuel-dev team mailing list archive

[Dmitry Borodaenko <dborodaenko@xxxxxxxxxxxx>]

Roman,

I don't think we should short-circuit triaging bugs like this: Triaged
status (according to https://wiki.openstack.org/wiki/BugTriage) means
that the solution is at least described in the bug, if not attached in
a patch. It's useful to distinguish this state from Confirmed (meaning
it can be replicated but root cause is not yet understood) and New
(meaning noone tried to replicate it yet). If a bug was assigned and
scheduled but hasn't even been confirmed it should remain New.

If you are looking to filter untouched bugs, I think the list of bugs
assigned to nobody is your best bet. Unfortunately I don't see a way
to filter for bugs without a milestone, so it might be difficult to
identify assigned but unscheduled bugs. Because of that we should be
careful to always set a milestone when processing bugs.

My 2c,
-DmitryB

On Mon, Mar 31, 2014 at 10:10 AM, Roman Alekseenkov
<ralekseenkov@xxxxxxxxxxxx> wrote:
> Folks,
>
> I noticed that we are doing good job in processing incoming bugs and setting
> 'Assignee' and 'Milestone' for them. However, the bugs do need to leave
> 'New' state when they get assigned to a specific release. The appropriate
> state for issues which are targeted to a particular release would be
> 'Triaged'.
>
> I.e. we should regularly work on cleaning up
> http://fuel-launchpad.mirantis.com/project/fuel/bug_table_for_status/New/None.
> Right now it has 32 bug count, and ideally it should be zero.
>
> Please take an action.
>
> Thanks,
> Roman
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Dmitry Borodaenko