Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Fwd: [eclipse-dev] Pinging old bugs

Of the bugs I filed over the last 2 years which haven't been fixed, I'd say 98% of them are still relevant. It seems like it would be a make-work exercise to have to reopen them all and say so.


From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: September 14, 2018 2:05 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Fwd: [eclipse-dev] Pinging old bugs

At this stage, I’m OK with closing bugs older than 2 years of inactivity. I would only do it for bugs that are major or below (not critical or blocking). That still leaves us around 1000.

I’m not as open to making that a bot’ed thing, but something we need to think about once in a while and purposefully decide. Bot’s tend to numb people, instead of causing action.

Unless we get a big injection of contribution from the community, we won’t have much of a chance to fix much at all. Coming up with a hot list of around 100, or even 20, would be a good outcome of the triage and help give us some focus.


From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Jonah Graham
Sent: Friday, September 14, 2018 5:54 AM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Fwd: [eclipse-dev] Pinging old bugs

Perhaps the bot is not the needed tool to achieve what I want.

We have nearly 4000 bugs, we are not likely to be able to review them in any reasonable timeframe. What I was hoping is that we could close all bugs with no activity in the last 2(?) years with a suitable comment, this would allow anyone with an interest in these long forgotten bugs to say so/reopen bugs. It would lead us to a more realistic situation where we are communicating our real intentions.

(NPM for a while had a 30 auto close for inactive issues<>, they have relaxed that a bit to 3 months now on the non-github issues they have moved to. )

Jonah Graham
Kichwa Coders Ltd.<>

On Tue, 11 Sep 2018 at 20:32, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx<mailto:dschaefer@xxxxxxxxxxxxxx>> wrote:
Checking my query, I see 1172 bugs are open and have been updated in the last three years.

There are 3749 bugs open all together dating back to the oldest from 2004.

I guess I’m wonder what we hope to achieve with this bot (other than filling my inbox with 2500+ emails). What benefits did the teams that are currently using it see?


From: cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx> <cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>> On Behalf Of Jonah Graham
Sent: Tuesday, September 11, 2018 2:49 PM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
Subject: [cdt-dev] Fwd: [eclipse-dev] Pinging old bugs

Hi folks,

The Eclipse platform bugs are getting a bot, I think it would be useful to have it done for CDT too ahead of the summit at EclipseCon Europe.

Any thoughts? I will raise request with webmaster@xxxxxxxxxxx<mailto:webmaster@xxxxxxxxxxx> if we have some consensus.


---------- Forwarded message ---------
From: Lars Vogel <lars.vogel@xxxxxxxxxxx<mailto:lars.vogel@xxxxxxxxxxx>>
Date: Tue, 11 Sep 2018, 19:18
Subject: [eclipse-dev] Pinging old bugs
To: General development mailing list of the Eclipse project. <eclipse-dev@xxxxxxxxxxx<mailto:eclipse-dev@xxxxxxxxxxx>>


the PMC decided to enable the "Is this bug still relevant" ping robot
for our TLP Eclipse bug components. See and

The robot starts his work tomorrow.

Best regards, Lars

Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx<mailto:lars.vogel@xxxxxxxxxxx>, Web:
eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top