+1 stop auto closing
Reasons
- 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.
- Auto-closing gives the impression “I don’t care”. Mark it stale instead
- What does auto-close achieve? I guess “nothing” apart from artificially reducing the bug count. It helps no one.
From: platform-dev <platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jean-Francois Maury
Sent: 17 February 2022 16:43
To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects
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@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
--
|
