Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] Using 'triaged' keyword instead of swt-triaged@xxxxxxxxxxx?


On Tue, Jun 6, 2017 at 4:32 AM, Lakshmi P Shanmugam <lakshmipriya.bms@xxxxxxxxx> wrote:
Hi Leo,

+1 to stop moving bugs to swt-triaged@xxxxxxxxxxx.
To mark the bug as triaged, we could change the Status field of bug from NEW to ASSIGNED. Some developers already do this, but not consistently.
May be all of us could follow this? We should update this in the triage page as well (once we agree).

I have concerns that  using "Assigned" status could be miss-understood as someone actually working on the bug (See workflow diagram below)

I.e, using "assigned" in this way might make users think that someone is working on the problem, where as in fact the bug is just in the queue to be worked on. (Think of users who stumble into bugs through stackoverflow or google..)

The 'triaged' keyword is a bit less intrusive and still allows us to filter bugs as triaged and non triaged.

Thoughts?




 
Thanks & Regards,
Lakshmi P Shanmugam

On 2 June 2017 at 00:42, Leo Ufimtsev <Leonidas@xxxxxxxxxx> wrote:
(I've had some issues with the mailing list, sorry if you received this message multiple times).

Hello folks,

I propose a change in how we triage bugs:

Our traditional triage (1*)  procedure is to inspect new bugs for proper classification, presence of a snippet etc and then re-assign those bugs from
platform-swt-inbox@xxxxxxxxxxx
However the problem here is that some developers follow platform-swt-inbox@xxxxxxxxxxx, but not swt-triaged@xxxxxxxxxxx. So triaged bugs seem to get less attention.

(Side note: their name is also quite similar (Project-SWT-Inbox) vs (Project-Inbox))

I propose instead that we add the 'triaged' keyword to bugs that were triaged and leave them assigned to Project-swt-inbox.

As for current bugs, we could slowly migrate all bugs to platform-swt-inbox and add 'triaged' keyword as we go along, closing irrelevant/old bugs. (as oppose to a bulk update).

I could update the relevant documentation for the job at hand. (1*).

Thoughts?

--

Leo Ufimtsev

Software Engineer

Red Hat


90 Eglinton Ave E #502,

Toronto, ON M4P 2Y3

Leonidas@xxxxxxxxxx  

CHAT:

  - IRC: http://webchat.freenode.net/?channels=#swt

  - MatterMost: https://mattermost.eclipse.org/eclipse/channels/platform-swt


_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev


_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev



--

Leo Ufimtsev

Software Engineer

Red Hat


90 Eglinton Ave E #502,

Toronto, ON M4P 2Y3

Leonidas@xxxxxxxxxx  

CHAT:

  - IRC: http://webchat.freenode.net/?channels=#swt

  - MatterMost: https://mattermost.eclipse.org/eclipse/channels/platform-swt

Back to the top