I definitely understand the negative comments about auto-closing bugs. For
context, I can say that we've been discussing the pros and cons of auto-closing
since the day the Eclipse Project had >1000 open bugs -- yes, that was many
years ago.
In those days, we could at least make the claim that we reviewed all the open
bugs occasionally, so we knew that they actually represented real issues in
current versions of Eclipse, or they were ideas about new things we could
conceive of doing at some point even if not in the short term.
The hard truth today, is as Alex said:
> In my opinion having bugs open without anyone looking into them for years
> is bad and even worse as it gives false sense of support which in reality is
> not there.
> I would change my mind if/when I see active triaging going on.
We talk about the harsh reaction people have about seeing their bugs
auto-closed, but we don't talk about the fact that our current way of working
leaves people with the feeling that reporting Eclipse bugs is a black hole.
Today, reporting a bug (or a design improvement) that isn’t a critical failure
on one of the main Eclipse developer flows is useless. I don’t know that
auto-closing bugs helps with that, but at least if the reporter still cares
about it, they have an opportunity to put it back in the committers view by
re-opening it. • that’s the piece of the auto-closing story that’s important:
If someone re-opens a bug after 2 years (or however long we chose), we sure as
heck better review it again. It is an issue that someone cares about.
So, you can see where this is going: My vote, FWIW, is -1 for “switch "off" bug
auto-closing”. I would be happy to see updated wording on the auto-close
message that made it clearer that re-opening the issue would cause it to be
re-reviewed by current contributors, but I believe we should continue to
auto-close.
McQ.
On 2022-02-17, 03:59, "platform-dev on behalf of Andrey Loskutov"
<platform-dev-boun...@eclipse.org on behalf of 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
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
