| Re: [platform-ui-dev] Automatically closing outdated bugs |
+1 for doing this. We can dream someone will come along and triage these bugs for us, but that's not overly likely. It's important to bring the number down to something manageable so we can get a real sense of where quality issues are and where we need to focus our limited time on.
BTW, I will be doing the same for CDT although we have only a quarter the open bugs platform UI has.
Doug.
From: platform-ui-dev-bounces@xxxxxxxxxxx [platform-ui-dev-bounces@xxxxxxxxxxx] on behalf of Lars Vogel [lars.vogel@xxxxxxxxx]
Sent: Monday, March 24, 2014 12:15 PM
To: Eclipse Platform UI component developers list.
Subject: Re: [platform-ui-dev] Automatically closing outdated bugs
Thanks for the input Eric. The possible implementation for this automatic process is currently discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=430819
Best regards, Lars
2014-03-24 15:42 GMT+01:00 Eric Moffatt <emoffatt@xxxxxxxxxx>:
Lars, I see two issues with this approach immediately:
1) At the very least we should introduce a new bucket for bug that auto-close, something like 'AWAITING INPUT'
2) In order to support 1) we'd still have to triage all these bugs sufficiently to determine whether the bug needs to go into the new bucket.
I'm all for doing something here since it's been a pain for time immemorial...;-). Perhaps we should track down some of the PhD candidates who want to use the Eclipse Bugzilla as there test case and see if they have any ideas.
Eric
Lars Vogel ---03/20/2014 11:33:59 AM---Hi, We have currently 5887 Bug in platform UI. I see the following problems
From:
Lars Vogel <lars.vogel@xxxxxxxxx>
To:
"Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>,
Date:
03/20/2014 11:33 AM
Subject:
[platform-ui-dev] Automatically closing outdated bugs
Sent by:
platform-ui-dev-bounces@xxxxxxxxxxx
Best regards, Lars_______________________________________________
Hi,
We have currently 5887 Bug in platform UI. I see the following problems with that:
1.) Lots of the reported problems may have been solved in the past
2.) Lots of the reported problems are not relevant any more
3.) Interested contributors have no way of weaving out 1.) or 2.)
4.) New bug reporters have no way to review them which leads to a lot of new bugs which report the same problem as an existing bug
5.) Committers cannot review this amount of bugs and critical or easy fixes are lost in this amount of bugs
So in the end this huge amount of bugs leads to a situation in which no one still looks at the old bugs. I
I therefore suggest that we establish the following guideline: Bug which have not been changed within the last 2 years are closed automatically. We could also filter out bugs which contain certain keywords.
The closing comment should be similar to the following:
-------------
This bug has not received any update within the last two years. Therefore we mark that bug as WORKSFORME. If the reported problem still exists, please reopen this bug.
--------------
I opened Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=430807 to discuss that.
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
