+1 to stop auto closing

During conference talks and presentations, we usually ask community to 
‘contribute’ bug reports. When they do, closing the bug as WONTFIX, many a 
times without any triage from the project side, gives the impression that we 
don’t value the effort of the ‘contributor’.
As a developer, I think auto closing is only helpful (to me) when there is no 
response for a long time on a bug marked as need-info, otherwise I have to add 
a comment and close it myself.

Thanks & Regards,
Lakshmi P Shanmugam

From: platform-dev <platform-dev-boun...@eclipse.org> on behalf of Vikas 
Chandra <vikas.chan...@in.ibm.com>
Reply to: "Eclipse platform general developers list." <platform-dev@eclipse.org>
Date: Tuesday, 22 February 2022 at 8:07 AM
To: "Eclipse platform general developers list." <platform-dev@eclipse.org>
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

+1 stop auto closing

Reasons

1)      Marking it as stale helps as the inbox manager/reporter/assignee goes 
or check if the bug is still valid and many times bugs have been
fixed as a result. Only thing is no more than 2-3 bugs per day per component 
should be marked as stale. If 100s of bugs r marked as stale on a single day,
it is counter-productive.

2)      Auto-closing gives the impression “I don’t care”. Mark it stale instead

3)      What does auto-close achieve? I guess “nothing”  apart from 
artificially reducing the bug count. It helps no one.

From: platform-dev <platform-dev-boun...@eclipse.org> On Behalf Of 
Jean-Francois Maury
Sent: 17 February 2022 16:43
To: Eclipse platform general developers list. <platform-dev@eclipse.org>
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all 
Eclipse platform projects

+1 stop auto closing

On Thu, Feb 17, 2022 at 9:58 AM Andrey Loskutov 
<losku...@gmx.de<mailto:losku...@gmx.de>> wrote:
Hi all,

this is a follow up on PMC response 
https://www.eclipse.org/lists/platform-dev/msg03319.html

As of today, this bug auto-closing is not active only for JDT project.

The proposal is to switch "off" bug auto-closing for the all Eclipse platform 
projects, including Platform, JDT, PDE und Equinox.
I don't think if we need an additional vote for PDE & Equinox, because the only 
active committers there are same as on the Eclipse platform.

Therefore I would like to start voting to stop auto-closing bugs in bugzilla, 
github, gitlab (or whatever else bug trackers we might use in the future) for 
all Eclipse platform development.

I think it is enough to post your +1 / 0 / -1 as a reply on this mailing list.
Everyone is welcome to vote but binding votes are committers`votes.
I would propose to conclude the vote by the end of the next week (25 February).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org<mailto:platform-dev@eclipse.org>
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev


--

Jeff Maury

Manager, DevTools

Red Hat EMEA<https://www.redhat.com>

jma...@redhat.com<mailto:jma...@redhat.com>
@RedHat<https://twitter.com/redhat>  Red Hat 
<https://www.linkedin.com/company/red-hat>   Red Hat 
<https://www.facebook.com/RedHatInc>
[Image removed by sender.]<https://www.redhat.com>
[Image removed by sender.]<https://redhat.com/summit>

_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Reply via email to